Add a rule non-boundary-event-overlaps-activity, which would give a warning if a catchEvent visually appears as a boundary event (e.g., overlaps a task).
Such situations could happen, if for example the positioning of elements is updated manually. They could also result from a modeling bug or using of modeling APIs.
Is your feature request related to a problem? Please describe
There were user reported problems, where an intermediateCatchEvent appeared visually as a boundary event. See https://jira.camunda.com/browse/SUPPORT-12954.
Describe the solution you'd like
Add a rule
non-boundary-event-overlaps-activity
, which would give a warning if a catchEvent visually appears as a boundary event (e.g., overlaps a task).Such situations could happen, if for example the positioning of elements is updated manually. They could also result from a modeling bug or using of modeling APIs.
Describe alternatives you've considered
n/a
Additional context
Could have been used to identify https://jira.camunda.com/browse/SUPPORT-12954