-
Notifications
You must be signed in to change notification settings - Fork 44
add stateValues to typegen output
#160
New issue
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
base: main
Are you sure you want to change the base?
Conversation
|
|
I know that it has been a while since you have created this PR - but could you rebase this on top of the main branch and add snapshots tests for the |
| ...toStatePaths(pathToStateValue(node.path)).map((path) => path.join('.')), | ||
| ]; | ||
| }, [] as string[]); | ||
| const states = allStateNodes.reduce((arr: StateValue[], node) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use StateValue type
every other change in this file is just formatting
Sorry I lost a bit of context on this since opening the PR but I hope these are the changes you requested 🙂 |
|
Yeah, this is what I had in mind - thank you 🙏 I'm gonna try to take a look at this soon |
.typegen.tsfiles in__examples__folder would not be deletedstateValuesto typegen output, so that it can be used in refactor: 🏷️ stronger types forStateValuewhen using Typegen xstate#3342