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
The schedule api is currently faulty where it only returns a struct with the name and the current start time. This issue is to build out that api to show the entire schedule as it stands with whatever events
The only question is how much business logic should be shown through the api. That is, show events and constraints both and let the user determine failure or just set some sort of flag in the struct. Saying that out loud seems to tend to the latter. That the node should hold state and expose that state through the api.
The text was updated successfully, but these errors were encountered:
The schedule api is currently faulty where it only returns a struct with the name and the current start time. This issue is to build out that api to show the entire schedule as it stands with whatever events
The only question is how much business logic should be shown through the api. That is, show events and constraints both and let the user determine failure or just set some sort of flag in the struct. Saying that out loud seems to tend to the latter. That the node should hold state and expose that state through the api.
The text was updated successfully, but these errors were encountered: