Activity Diagram for Frontend #93
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#93
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?
We need an activity diagram to model how our frontend works.
Parent Issue: #84
The Activity Diagram illustrates the flow and communication between different frontend files. After React starts we call the view we want depending on what the card should show. We then set the initial state to loading, fetch the desired data and change the state depending on if the data was fetched succesfully or not. If an error occured, we should get a message displaying the error. If data was fetched succesfully, we use the existing "Card" to display the data with the correct layout.
Reviewed, looked good