You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Symptom: consistency validation can report duplicate output variables for values declared in mutually exclusive IF branches after exec builds the graph. A targeted Mendix 9 validation pass also showed that emitting ExpressionCase directly breaks legacy MPRs because that metamodel stores boolean branches as enumeration-style case values.
Root cause: IF sequence flows used EnumerationCase values as the only in-memory representation. That conflates IF branch cases with real enum split cases, but the writer also needs to honor the target Mendix version when serializing the case object.
Fix: represent true/false IF branch flows as ExpressionCase internally, keep EnumerationCase for real enum split values, serialize ExpressionCase as ExpressionCase for modern MPRs, and downgrade it to EnumerationCase when writing Mendix 9 projects.
Tests: make build, make test, make lint-go.
0 commit comments