[Card] Card class diagram #129
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#129
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?
Create a class diagram that shows relationship between Cards, Views and their respective functions.
Parent Issues: #6 #130
Related Issues: #135
Cards class diagramto [Card] Card class diagramPrototype to work from.
Overview
The view gets called from App.js and in turn the view calls both the hook for data and the Card to get a frame rendered, before ruturning an complete View render to the app.
Missing
Currently every view use its own logic to present the data. There might be another "layer"/component for logic in the view. This will be logic for text,pictures and graphs. The point is to reduce duplicated code and make the diffrent viewes more uniform.
Drawio file to change moddel if chages happans.
Right now the class diagram is stated as components, functions missing types and private/public as well as attribute such as data/loading/error which are constants from the object "useTemperature".
Suggestion:
Perhaps make it more clear on what type of diagram that is used.
Changed private/public symbols and added what data is contained in the diffrent varibles
new Drawio file
The updated diagram is now clearer and more consistent. Distinction between components and classes has been improved.
Types have been added to attributes , and they return values (e.g., string, json, bool) and makes the design easier to understand.
Types have been implemented for private and public with (+ and - ), and previous ambiguity around data, loading and error has been solved.
The design is now better and communicates better with structure and responsisbility between components.