DESCRIBE MICROFLOW emits default anchor fragments that create cosmetic drift

[hjotha]

Problem:

DESCRIBE MICROFLOW prints explicit anchor fragments for connection sides that match MDL defaults. Re-execution can omit or normalize those defaults, creating noisy cosmetic diffs.

Expected:

Describe output should omit anchor fragments that are equivalent to the default connection sides, while still preserving non-default anchors.

Impact:

Roundtrip audits produce avoidable cosmetic mismatch noise.

Proposed fix:

Suppress default anchor fragments for regular and split branch flows.

[github-actions]

Issue Triage

Summary
The issue reports that DESCRIBE MICROFLOW prints anchor fragments that are identical to the MDL defaults, leading to unnecessary cosmetic differences when the MDL script is re‑executed.

Checklist for bug‑report completeness

Required info	Present?	Notes
mxcli version (output of mxcli --version or commit/build)	❌	Not mentioned
Mendix version of the project (e.g., 10.x, 9.x)	❌	Not mentioned
Scenario – what the user was trying to do (MDL script, CLI command, etc.)	⚠️	Implicitly “running DESCRIBE MICROFLOW”, but no concrete command or script shown
Expected output – what should have happened	✅	Stated: omit anchor fragments that match MDL defaults
Experienced output – what actually happened (error, wrong result, crash)	⚠️	Described generally (“prints explicit anchor fragments for connection sides that match MDL defaults”), but no exact output example or error message
AI bug report – output of mxcli diag --bundle or at least the session log	❌	Not provided

What’s needed
To help us reproduce and fix this, could you please add:

1. The exact version of mxcli you’re using (mxcli --version).
2. The Mendix version of the project you’re working on.
3. The precise command you ran (including any arguments) and a short snippet of the MDL script, if applicable.
4. An example of the actual output you saw from DESCRIBE MICROFLOW (showing the unwanted anchor fragments).
5. If possible, run mxcli diag --bundle and attach the resulting bundle, or at least share the session log from the command.

Thanks for reporting this – with those details we’ll be able to investigate and implement the fix quickly!

---

Automated triage via OpenRouter — workflow source