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.

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

The way Options interact with their Commands right now is bad #8

Open
twof opened this issue Dec 16, 2017 · 1 comment
Open

The way Options interact with their Commands right now is bad #8

twof opened this issue Dec 16, 2017 · 1 comment
Assignees

Comments

@twof
Copy link
Owner

twof commented Dec 16, 2017

State is bad because it removes type safety and forcing the user to use string keys makes the whole system extremely prone to typos.

The second point is solved slightly by using constants, but there's no way to enforce that right now.

Will update this with more info. Experimentation will be happening in the StateExperimentation branch.

@twof twof self-assigned this Dec 16, 2017
@twof
Copy link
Owner Author

twof commented Dec 22, 2018

Could use the class method for type safe state and then also conform dictionary to the necessary protocols to make it usable as lightweight unsafe state should people want it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant