[Card] Sequence diagram for cards/views #135
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#135
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 Issues: #129
Parent Issues: #6 #130
Sequens diagram
This shows how data is transfered from a view call in the app untill its rendered.
First the app calls the view for a render.
Then the View needs to call both Hook(Api) for data and Card to render the frame.
When the View have recived both the data and the rendered frame it can return a complete rendered View to the app.
Missing
In the future there might be a logic layer to give a uniform view of the diffrent type of cards like text,picture and graph. This would also be called from the view.
File to change moddel if chages happans.
The "sequence" between view and hook is not an "ApiCall", rather an import. The actual "Hook" makes the "ApiCall", otherwise I think that the diagram is good.
I have added an Api so the Hook calls the Api to get the data before returning it.
Drawio file if chages are needed later.
Looks good! Show clearly how the different parts of the system interacts with each other.
Added to wiki