check --references should validate DYNAMICTEXT ContentParams type compatibility

[engalar]

Description

mxcli check script.mdl -p app.mpr --references does not validate that DYNAMICTEXT ContentParams attribute bindings are type-compatible. When binding an Integer attribute using simple AttrName syntax inside a DataView, the check passes but the page renders incorrectly at runtime (empty or error).

Steps to Reproduce

-- DashboardData entity has TotalOrders: Integer

CREATE PAGE MyModule.Dashboard (...) {
  DATAVIEW dv (DataSource: MICROFLOW MyModule.DS_GetData) {
    DYNAMICTEXT txt (Content: '{1}', ContentParams: [{1} = TotalOrders], RenderMode: H2)
  }
}

mxcli check script.mdl -p app.mpr --references
# ✓ All references valid  ← should warn or fail

Expected Behavior

Either:

1. Reference validation should warn that TotalOrders (Integer) needs toString() wrapping for DYNAMICTEXT ContentParams
2. Or mxcli should automatically emit the correct binding syntax toString($currentObject/TotalOrders) when the attribute type is non-String

Correct Syntax

DYNAMICTEXT txt (Content: '{1}', ContentParams: [{1} = toString($currentObject/TotalOrders)], RenderMode: H2)

Context

The create-page.md skill documentation states that AttrName works in DataView context for ContentParams, but this only holds for String-type attributes. Non-String types (Integer, Decimal, DateTime, Boolean) require explicit toString($currentObject/AttrName) syntax. This gap in documentation + validation causes AI agents to generate pages that pass all checks but fail at runtime.

[github-actions]

Issue Triage

Summary:
The mxcli check --references command does not detect type‑incompatible bindings in DYNAMICTEXT ContentParams, allowing invalid Integer (or other non‑String) attribute references to pass validation and cause runtime rendering issues.

Checklist of required bug‑report information

Required info	Present?	Notes
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	mxcli check script.mdl -p app.mpr --references on a DataView with DYNAMICTEXT
Expected output	✅	Should warn/fail or auto‑correct the binding
Experienced output	✅	Check reports “All references valid” (no warning/failure)
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
Please add the output of mxcli --version (or the commit/build you’re using) and the Mendix version of the .mpr file you’re checking. If possible, also attach the session log from mxcli diag --bundle so we can reproduce the exact environment.

Thanks for reporting this—once we have those details we can investigate the validation gap!

---

Automated triage via OpenRouter — workflow source

[engalar]

[engalar]

Not support specify Parameter type

[ako]

Fixed in commit `6ed3dcc`. The page builder now auto-converts non-String attribute bindings in ContentParams to `toString()` expressions.

Before:
```sql
DYNAMICTEXT txt (Content: '{1}', ContentParams: [{1} = TotalOrders])
-- Generated: AttributeRef = "Module.Entity.TotalOrders" (broken for Integer)
```

After:
```sql
DYNAMICTEXT txt (Content: '{1}', ContentParams: [{1} = TotalOrders])
-- Generated: Expression = "toString($currentObject/TotalOrders)" (works for all types)
```

String attributes continue to use direct AttributeRef (no change). The conversion uses the existing `findAttributeType()` infrastructure and fails open — if the attribute type can't be determined, it assumes String to preserve backward compatibility.

No validation warning is needed since the builder now produces correct output automatically.