Problem
Scripts that pass mxcli check can still produce numerous semantic errors in mx check (Mendix Validator): CE0111 (duplicate variables), CE0109 (undefined variables), CE0053 (invalid types), CE0066 (stale entity access). Today there's no way to get Validator-equivalent feedback without launching Studio Pro / mx.
Current behavior
mxcli check performs syntax parsing + reserved-word checks + some microflow body validation (cmd/mxcli/cmd_check.go:107-136). --references adds reference/conflict validation but requires -p <project> (:154-206). There is no --full / semantic mode, and no flag to run the equivalent of mx check.
Request
Add mxcli check --full performing semantic validation equivalent to mx check (variable scope/uniqueness, type resolution, entity-access freshness, …).
Related (subsets of this umbrella)
A --full mode would likely subsume/aggregate these; consider whether to implement them under this umbrella or keep granular and have --full orchestrate them.
Source: customer feedback batch (2026-06). Reporter: Miwa. Reporter severity: 5/5.
Filed after codebase investigation at 297e0b0a.
Problem
Scripts that pass
mxcli checkcan still produce numerous semantic errors inmx check(Mendix Validator): CE0111 (duplicate variables), CE0109 (undefined variables), CE0053 (invalid types), CE0066 (stale entity access). Today there's no way to get Validator-equivalent feedback without launching Studio Pro /mx.Current behavior
mxcli checkperforms syntax parsing + reserved-word checks + some microflow body validation (cmd/mxcli/cmd_check.go:107-136).--referencesadds reference/conflict validation but requires-p <project>(:154-206). There is no--full/ semantic mode, and no flag to run the equivalent ofmx check.Request
Add
mxcli check --fullperforming semantic validation equivalent tomx check(variable scope/uniqueness, type resolution, entity-access freshness, …).Related (subsets of this umbrella)
mxcli checkmxcli checkshould hint at common expression/syntax issuesmxcli checkA
--fullmode would likely subsume/aggregate these; consider whether to implement them under this umbrella or keep granular and have--fullorchestrate them.Source: customer feedback batch (2026-06). Reporter: Miwa. Reporter severity: 5/5.
Filed after codebase investigation at
297e0b0a.