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

You should always be able to transition to the current state of the FSM. #12

Closed
mjstahl opened this issue May 2, 2019 · 2 comments
Closed

You should always be able to transition to the current state of the FSM. #12

mjstahl opened this issue May 2, 2019 · 2 comments

Comments

@mjstahl
Copy link
Collaborator

mjstahl commented May 2, 2019

Right now, the current state of the FSM is not (automatically) a state that can be transitioned too. It has to be written that way.

Each state should always include itself as a transition option.
@mjstahl
Copy link
Collaborator Author

mjstahl commented May 13, 2019

Then remove forceUpdate from being exported

@mjstahl
Copy link
Collaborator Author

mjstahl commented May 13, 2019 •
edited

Removing forceUpdate for routing is more difficult. It cannot be removed until I figure out how to update app state without changing the route.

We will make this a different issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mjstahl