Create class diagram for Frontend class #149
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
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#149
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?
Related to issue Class Diagrams #91
I start with this now
I'm not sure if I'm thinking about this in the best way. I've been forced to make some assumptions since there's no discrete classes, and I chose to write the method-names and attributes in a describing and abstract way to not make it too clogged for further scaling later.
Current prototype:
@b24hugst I think you can move your diagram to wiki then we close this issue.
@a24sakma This is very outdated though haha I don't think anything in this diagram is correct anymore.
@b24hugst will you try to update the diagram probably next week. When we are trying to document for the next group
@a24sakma Yes I could. Will probably take some time though but next week sounds good.
This is not needed any more as we went through the models. I close this issue.