-
Notifications
You must be signed in to change notification settings - Fork 481
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
Warn users about hidden sequence flows #2994
Comments
Thanks for your report. We'll investigate if moving sequence flows to the front is a quick win or if we need another way to indicate such flows. |
If that does not work linting could be an option. |
Moved to backlog, we could consider this as a warning in the future. |
Somehow it was still |
There will be no hidden sequence flow once bpmn-io/bpmn-js#1717 is integrated. |
Problem you would like to solve
When editing a model it could occur that some sequence flows are seemingly connected in one way:
But in reality the sequence flows behind the gateway:
In the first image it's very hard to see that the sequence flows doesn't target the gateway, but goes through it and targets the task. It would be great if we could improve this visually, or warn the user with linting that a flow is hidden.
Proposed solution
Move sequence flows to the foreground of the process.
Alternatives considered
Have linting detect when a sequence flow is hidden underneath some other element, giving users a warning when this is the case.
Additional context
No response
The text was updated successfully, but these errors were encountered: