You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to dynamically update timers, it would be useful to have a field in the schedule endpoint that gives start and end times for each block. Just returning timestamps like it has in the picture would be fine, but it would be best to return a formatted date object whether that is in a string or a number of seconds or milliseconds in order to reduce complication on the front end.
For formatting, a possibility would be "blockTimes": [{"block": "A", "start": "1514001963005", "end": "1514001979926"},...]
This would allow for easy access to both the block letter and timing information as well as opening possibilities for additional fields to be added to each block without breaking existing applications.
The text was updated successfully, but these errors were encountered:
In order to dynamically update timers, it would be useful to have a field in the schedule endpoint that gives start and end times for each block. Just returning timestamps like it has in the picture would be fine, but it would be best to return a formatted date object whether that is in a string or a number of seconds or milliseconds in order to reduce complication on the front end.
For formatting, a possibility would be
"blockTimes": [{"block": "A", "start": "1514001963005", "end": "1514001979926"},...]
This would allow for easy access to both the block letter and timing information as well as opening possibilities for additional fields to be added to each block without breaking existing applications.
The text was updated successfully, but these errors were encountered: