We need to do research on what cards should automatically update #742
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
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#742
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?
Description
In issue #702 the card TemperatureView now updates automatically.
The next step is to decides what cards automaticly should be updated and how often this should occur.
What needs to be done
ParkingView:
-Data is fetched once
-Suggested interval: every 1–2 minutes
-Reason: Parking availability can change frequently
-Auto-update can be added
The table below shows what cards should be automatically updated. This excludes the TemperatureView and should exclude the ClockView since the update is implemented but because it was recently created and still needs review.
Reasoning looks solid, i think the high end of the updating frequency could be preferred to keep the amount of data being fetch as low as possible while still keeping the cards fresh
Great review. I agree that the high end should be used