Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #28322 [Workflow] Make sure we do not run the next transition on …
…an updated state (Nyholm) This PR was squashed before being merged into the 4.1 branch (closes #28322). Discussion ---------- [Workflow] Make sure we do not run the next transition on an updated state | Q | A | ------------- | --- | Branch? | 4.1 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | When you have a workflow like this, where all transitions are named the same. ![php](https://user-images.githubusercontent.com/1275206/44908106-87914680-ad1a-11e8-9c6f-e58de4b255e8.png) The current behavior on `$stateMachine->apply($object, 'next')` is that it will go to "done". It will do this because it checks the current "froms" at each iteration in the loop in `apply()`. It should check the valid transition before it actually apply them. Commits ------- d9dda76 [Workflow] Make sure we do not run the next transition on an updated state
- Loading branch information