RENAME MODULE fails: case mismatch between visitor and executor

[retran]

Description

RENAME MODULE OldModule TO NewModule; fails with:

Error: rename not supported for MODULE

Root Cause

Case mismatch between visitor and executor:

• Visitor (visitor_entity.go:841): sets ObjectType: "MODULE" (uppercase)
• Executor (cmd_rename.go:38): checks case "module": (lowercase)

The executor's switch statement at line 38 matches "module" but the visitor produces "MODULE", so it falls through to the default case which returns NewUnsupported.

Fix

Either:

• Change visitor_entity.go:841 to ObjectType: "module" (consistent with all other rename types which are lowercase)
• Or add strings.ToLower(s.ObjectType) in the switch

Reproduction

mxcli -c "CREATE MODULE OldMod; RENAME MODULE OldMod TO NewMod;" -p app.mpr
# Error: rename not supported for MODULE

Severity

Medium — feature is fully implemented but unreachable due to a one-character casing bug.

[github-actions]

Issue Triage

Summary:
The RENAME MODULE command fails because the visitor returns "MODULE" (uppercase) while the executor expects "module" (lowercase), causing a case‑mismatch error.

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	MDL script via mxcli -c \"CREATE MODULE OldMod; RENAME MODULE OldMod TO NewMod;\"
Expected output	⚠️	Implicit (rename should succeed) but not explicitly stated
Experienced output	✅	Error: rename not supported for MODULE
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:

• The version of mxcli you’re using (output of mxcli --version or commit/build info).
• The Mendix version of the .mpr file you’re processing.
• An explicit statement of what you expected to happen (e.g., the module should be renamed without error).
• A diagnostic bundle (mxcli diag --bundle) or at least the session log to help confirm the environment.

Could you please add those details? Once we have them, we’ll be able to verify and fix the issue quickly. Thanks for reporting!

---

Automated triage via OpenRouter — workflow source