We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello So I needed a state machine in which a self loop would trigger a state entering method. For example:
const fsm = new StateMachine({ init: 'waiting', transitions: [ { name: 'transferred', from: 'waiting', to: 'waiting' }, ], methods: { onWaiting: function () { console.log('Im waiting') }, }, })
The application was not logging twice when I tested this:
fsm.transferred()
So I appended to the object provided to the constructor, the following key:value pair observeUnchangedState: true
observeUnchangedState: true
Because I saw this condition in the source code. So, will I get unexpected side effects when using this? I'm asking because this is not documented.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello
So I needed a state machine in which a self loop would trigger a state entering method.
For example:
The application was not logging twice when I tested this:
So I appended to the object provided to the constructor, the following key:value pair
observeUnchangedState: true
Because I saw this condition in the source code.
So, will I get unexpected side effects when using this?
I'm asking because this is not documented.
The text was updated successfully, but these errors were encountered: