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

Fix FSM getting stuck into "*" state #64

Merged
merged 3 commits into from Nov 19, 2016

Conversation

Projects
None yet
2 participants
@QuentinRoy
Contributor

QuentinRoy commented Aug 15, 2014

With double WILDCARD events, e.g. { name: 'myevent', from: '*' } the state machine ends up in the state '*'.
This pull request fixes it : the FSM now stays in the same state.

Double WILDCARD events may be useful if an event can be triggered at any moment while only triggering a transition from some states.

@jakesgordon

This comment has been minimized.

Show comment
Hide comment
@jakesgordon

jakesgordon Jan 17, 2015

Owner

Can you add a test for this case please?
Thanks

Owner

jakesgordon commented Jan 17, 2015

Can you add a test for this case please?
Thanks

@QuentinRoy

This comment has been minimized.

Show comment
Hide comment
@QuentinRoy

QuentinRoy Nov 12, 2015

Contributor

Any feedback on this issue?

Contributor

QuentinRoy commented Nov 12, 2015

Any feedback on this issue?

@jakesgordon jakesgordon added the v2.4 label Nov 18, 2016

@jakesgordon jakesgordon merged commit ffec3f4 into jakesgordon:master Nov 19, 2016

jakesgordon added a commit that referenced this pull request Nov 19, 2016

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