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
As referenced in #20, transition functions can be shared across FSM to be more memory efficient since they don't need a reference to their parent FSM.
Allow for transition functions to be set either in the constructor of the fsm or as a property.
var fsm = new typestate.FiniteStateMachine<States>(State.StartState, [...transistionFunctions]); // or var fsm = new typestate.FinitStateMachine<States>(State.StartState); fsm.functions = [...transitionFunctions];
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug
As referenced in #20, transition functions can be shared across FSM to be more memory efficient since they don't need a reference to their parent FSM.
Proposed fix
Allow for transition functions to be set either in the constructor of the fsm or as a property.
The text was updated successfully, but these errors were encountered: