This repository has been archived by the owner on Mar 4, 2022. It is now read-only.
Parse description field in StateNode #18
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/statelyai/xstate-parser-example-site/5thkY3JzhhQmcojDBzHtZAE5axzA |
with-heart
force-pushed
the
parse-description-field
branch
from
793bf8f
to
b6bb3dc
Compare
with-heart
force-pushed
the
parse-description-field
branch
from
b6bb3dc
to
47a1af0
Compare
|
@with-heart Thanks so much for the PR! This repo's undergoing some changes - I'm moving it to be a package of a monorepo at https://github.com/statelyai/xstate-vscode. I'll merge your changes there once that refactor is complete. |
|
@mattpocock NICE! Let me know if there's anything I can do to help with the transition :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves #15 by adding the exact diff code supplied by @r-moore in that issue. Also added an
examplestest for the rootdescriptionand a nesteddescription.