-
Notifications
You must be signed in to change notification settings - Fork 601
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
Action is not parallel #336
Comments
Give me some time to play with this sample. Clearly something is happening parallel as otherwise |
@jvalkeal
So I added
Finally, console log changed:
Cheers, Action become pallallel! |
I ran the code and indeed it's just like you mentioned. I need to add few tests to better understand this specific behaviour. Thing is that you can add transitions which are potentially triggered by same event in every machine in a s state hierarchy. If deepest submachine state don't accept event then it's checked from parent, etc. Things here still goes via separate executors in a different submachines but things seem to work differently because you machine is not driven by events and everything happens automatically via anonymous transitions initiated from initial states. All this start to happen when you start a root machine. I still don't how this behaves so I'll try to something about it. |
According to But Root statemachine have all transition, after root executor start child executor, it continue to next loop as follow code, and get next transition(should be child transition), so the action will be executed by root statemachine synchronous.
|
Version: 1.2.3.RELEASE
The test code:
The Console log:
If parallel, the log would like this:
The text was updated successfully, but these errors were encountered: