Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should the WKT API be more restrictive? #56

Open
hannobraun opened this issue Mar 9, 2018 · 0 comments
Open

Should the WKT API be more restrictive? #56

hannobraun opened this issue Mar 9, 2018 · 0 comments
Labels
help wanted type: design

Comments

@hannobraun
Copy link
Member

Currently, the WKT API isn't very restrictive. Some things that it allows:

  • Select a clock that is not enabled.
  • Attempt to start the timer while the selected clock is not enabled.
  • Disable the clock while the timer is running.

It would be relatively straight-forward to fix all of this, but I'm wondering which of those should be prevented, and which are valid use cases. Any feedback on this issue is much appreciated!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted type: design
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hannobraun