xstate
xstate copied to clipboard
[do not merge] Allow wildcard transitions to act as "error handlers"
While investigating https://github.com/statelyai/xstate/issues/2919 I've noticed some things and played around with minor code adjustments.
⚠️ No Changeset found
Latest commit: 1afe0e6832892f25a8fb043d06137dd9a577f9e6
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a 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 1afe0e6832892f25a8fb043d06137dd9a577f9e6:
| Sandbox | Source |
|---|---|
| XState Example Template | Configuration |
| XState React Template | Configuration |
Let's prefer onError on state?
Decision:
- Do not allow built-in events to be captured by wildcards
- Do not allow errors to be captured by wildcards (these are built-in events anyway)
