Closed nikku closed 8 months ago
Implicit starts are considered a bad practice, as they make diagrams confusing, often times not matching the actual execution semantics:
Explicit modeling (cf. fake-join) encourages good practices, and creation of a little more verbose, albeit understandable, diagrams.
fake-join
implicit-start
error
None.
Closed via https://github.com/bpmn-io/bpmnlint/pull/103.
The rule should detect the following modeling patterns
How does the rule improve the BPMN diagram?
Implicit starts are considered a bad practice, as they make diagrams confusing, often times not matching the actual execution semantics:
Explicit modeling (cf.
fake-join
) encourages good practices, and creation of a little more verbose, albeit understandable, diagrams.Rule Details
implicit-start
error
What alternatives did you consider?
None.