Restructuring of the roombooking service's code #724
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#724
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As discussed in #191, this service needs a restructuring of code to follow better OOP/Software Engineering structure.
The diagram in #590 serves as a general guide for the structure needed. (Mostly the top 'service' part's structure of interfaces and separation of endpoints and methods etc.)
there is a new diagram of the planed structure of roombooking here #591
This has been merged in this pr #882. I close this issue.