Open Diokuz opened 9 months ago
Hey!
We have a beta feature currently available to Stately Pro subscribers where you can export the state machines you create to Markdown:
Here is what it looks like:
The initial state of the git bisect flow.
On SET_GOOD_COMMIT
:
goodCommit
: "{{(_, event) => event.commit}}"
On SET_BAD_COMMIT
:
badCommit
: "{{(_, event) => event.commit}}"
On START_BISECT
:
State representing the bisecting process.
Testing a commit to find if it is good or bad.
On GOOD_COMMIT_FOUND
:
On BAD_COMMIT_FOUND
:
On BISECT_COMPLETE
:
A good commit has been found during the bisect process.
On REVERT_COMMIT
:
A bad commit has been found during the bisect process.
On REVERT_COMMIT
:
The git bisect process has completed successfully.
Reverting a commit to continue the bisect process.
On REVERT_COMPLETE
:
On REVERT_FAILED
:
Reverting a commit failed, so the bisect process cannot continue.
On RESUME_BISECT
:
Hi there!
I found XState, and it is great! I can describe and use a state machine, I can visualize it, I can observe a state graph, and even generate test-cases from it.
Whats about documentation? I failed to google anything related https://www.google.com/search?q=how+to+generate+documentation+from+xstate
I found some docs for meta and tags, but failed to find any tools to generate docs from it.
Also, I have this message in my vscode when hovering the
meta
property:Do you guys have any plans for tooling which would generate documentation from xstate model?