-
-
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] Remove autoForward
#3889
[v5] Remove autoForward
#3889
Conversation
🦋 Changeset detectedLatest commit: 234d416 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 234d416:
|
85548f3
to
8c52329
Compare
* Remove more `autoForward` leftovers * Remove unused import
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
fb70dac
to
c21e2eb
Compare
…toforward # Conflicts: # packages/core/test/invoke.test.ts
The recommended pattern moving forward would be to explicitly
sendTo(...)
events to actors.There are still some SCXML tests that depend onXState will no longer supportautoForward
.autoForward
in SCXML.