Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #51214 [Workflow] Use TRANSITION_TYPE_WORKFLOW for rendering work…
…flow in profiler (lyrixx) This PR was merged into the 6.4 branch. Discussion ---------- [Workflow] Use TRANSITION_TYPE_WORKFLOW for rendering workflow in profiler | Q | A | ------------- | --- | Branch? | 6.4 | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | | License | MIT | Doc PR | --- This one is a bit special. Usually a state machine render like this: ![image](https://github.com/symfony/symfony/assets/408368/50f45620-aa88-4fc8-97c2-1049c08b2ee7) As you can see, **transitions** (ex: `start_process`) are not real nodes. They are arrows. And it's not possible to attach events on arrows, only on nodes. That's why I add this hybrid mode, where state machine are rendered like a workflow. It means transitions are renderered as node: ![image](https://github.com/symfony/symfony/assets/408368/80f6731a-2d02-4eab-be2d-77ab67495006) Now, we can attach event on transition nodes. Commits ------- 0cdf2b8 [Workflow] Use TRANSITION_TYPE_WORKFLOW for rendering workflow in profiler
- Loading branch information