Unknown attribute type silently interpreted as enumeration reference

[retran]

Impact

Typos in type names produce corrupt models referencing non-existent enumerations instead of failing fast.

Steps to Reproduce

1. Run CREATE PERSISTENT ENTITY M.E (Field1: invalidtype);
2. Command succeeds
3. Field1 stored as Enumeration(invalidtype) — references non-existent enum

Expected Behavior

Error for unknown or unresolvable type name.

Severity

Low — fails silently; caught later by Studio Pro validation.

---

Discovered during AI-assisted manual testing session (2026-04-29, mxcli v0.7.0-257-ga07e7e0).

[github-actions]

Issue Triage

Summary:
The issue reports that mxcli silently treats an unknown attribute type as an enumeration reference instead of failing with an error.

Checklist (bug report):

Required info	Present?	Details
mxcli version	✅	v0.7.0-257-ga07e7e0 (from the issue)
Mendix version	❌	Not mentioned
Scenario (what was tried)	✅	Running CREATE PERSISTENT ENTITY M.E (Field1: invalidtype);
Expected output	✅	Error for unknown/unresolvable type name
Experienced output	✅	Command succeeds; field stored as Enumeration(invalidtype)
AI bug report (mxcli diag --bundle or session log)	❌	Only a note about discovery; no bundle/log attached

Missing information:

• The Mendix version of the project being processed.
• The output of mxcli diag --bundle (or at least the session log) to help reproduce the environment.

Could you please add those details? Thanks for the report!

---

Automated triage via OpenRouter — workflow source