-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[v5] Action types #4180
[v5] Action types #4180
Conversation
🦋 Changeset detectedLatest commit: 7c332b8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7c332b8:
|
f4e0afb
to
60735ca
Compare
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.
We could add TAction
to StateNode
as well - but I kinda feel that state nodes should mostly be treated as internal data structures. Even if we expose them... people should just treat things as unknown
etc as that's mostly useful for inspection, analysis etc and that kind of code is super generic. Thoughts?
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.
Agree that StateNode
should be internal, so it's your call whether to add it or not. Can always be added later
No description provided.