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
The main case I'm aware of is when an event only triggers actions but doesn't change the state.
{ "initial": "initial", "states": { "initial": { "on": { "LOG": { "actions": ["log"] } } } } }
I know the example doesn't make a lot of sense on it's own, but it's a minimal reproduction case. It is displayed correctly in the interactive viz but fails in this sandbox with latest versions of xstate and xstate-plantuml
xstate
xstate-plantuml
I tweaked the code to get some output for a state machine that makes heavy use of it, but I'm not sure the way I have done it considers all cases.
The text was updated successfully, but these errors were encountered:
fix(Buffer): Handle "empty" parts in appendf
appendf
e268ddb
- Makes it possible to pass an empty target as described in #38 without causing syntax errors.
Successfully merging a pull request may close this issue.
The main case I'm aware of is when an event only triggers actions but doesn't change the state.
I know the example doesn't make a lot of sense on it's own, but it's a minimal reproduction case.
It is displayed correctly in the interactive viz but fails in this sandbox with latest versions of
xstate
andxstate-plantuml
I tweaked the code to get some output for a state machine that makes heavy use of it, but I'm not sure the way I have done it considers all cases.
The text was updated successfully, but these errors were encountered: