no-disconnected rule should also check for existence of incoming and outgoing connection, where needed

bpmn-io / bpmnlint

Validate BPMN diagrams based on configurable lint rules.

MIT License

121 stars 36 forks source link

no-disconnected rule should also check for existence of incoming and outgoing connection, where needed #70

Closed MaxTru closed 2 years ago

MaxTru commented 2 years ago

Is your feature request related to a problem? Please describe

Currently the no-disconnected rule checks whether an incoming or outgoing connection exists
However, in many cases (not in all though), an incoming and outgoing connection is needed

Describe the solution you'd like

no-disconnected rule should also check for existence of incoming and outgoing connection, where needed

Describe alternatives you've considered

Implement as seperate rule.

Additional context

nikku commented 2 years ago

This is not actionable at this point. Could you share a concrete example where incoming and outgoing are needed?

MaxTru commented 2 years ago

Hmmm. I double checked the BPMN spec to find some specifcs about this but was not succesful.

My assumption would be:

for example a service task should always have an input and an output sequence flow right?

However, as said - I did not find specifics about this in the spec. Will close for now.

nikku commented 2 years ago

That is my intuition. Any element that is not connected from a start event is an implicit start event in BPMN. We could argue whether that shall be a "discouraged" modeling pattern. I think it should. no-implicit-start or the like.

Still, if we want this re-opened, please share a concrete instance of the issue you want highlighted / addressed.