-
Notifications
You must be signed in to change notification settings - Fork 14
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
Missing label validation for gateway #94
Comments
@danielriedmueller Why would a joining gateway need a label? What would be the user problem this solves? |
Closing this as not planned, but happy to hear your thoughts to learn. |
Thanks for your response, that makes sense. |
We've seen and discussed bpmn-io/bpmnlint#153. As we evolve our rule set and do more "at the core" we have to ensure to provide value to many. Your scenario "all elements have to be named" seems to be special. And completely (everywhere) enforcing unique labels does not make sense from the pure BPMN standpoint, too. What bpmnlint offers is the ability to configure rules. So we could build (or you could contribute) changes that are configurable, but work per default in a reasonable (for many) way. |
Describe the Bug
If a gateway has two inputs and one output and no label,
it shows no error.
Expected Behavior
All gateways must have a label, regardless of connections.
Its expected that the linter shows an error.
BMPN to reproduce:
The text was updated successfully, but these errors were encountered: