Skip to content

Fix nightly on Mendix 10.24: drop 11.x-only design property from 15b - #47

Merged
ako merged 1 commit into
mainfrom
fix/nightly-10.24-15b-design-property
Jul 27, 2026
Merged

Fix nightly on Mendix 10.24: drop 11.x-only design property from 15b#47
ako merged 1 commit into
mainfrom
fix/nightly-10.24-15b-design-property

Conversation

@ako

@ako ako commented Jul 27, 2026

Copy link
Copy Markdown
Owner

Summary

The nightly matrix (Mendix 10.24 / 11.6 / 11.12) failed only on 10.24:

TestMxCheck_DoctypeScripts/15b-fragment-slots-examples  (both engines)
  [CE6083] "Design property Card style is not supported by your theme" at Container 'cardWrap' (×4)

Card style is an Atlas v3 (11.x) design property; the 10.x Atlas theme doesn't define it. Same class of nightly-only, version-specific failure as the 15c building-block fix (#43).

Fix — remove, don't gate

The property sat on the shared define fragment Card, instantiated by every page in the file, so a -- @version: gate would have to gate the whole file and lose all 10.24 coverage of the content-slot feature 15b actually demonstrates. The design property was incidental (design properties are covered by 12-styling-examples.mdl, gated 11.0+), so I dropped it and kept class: 'card' — Atlas card styling that works on every Mendix version.

Gate-vs-remove rule (now in fix-issue.md): if the version-specific construct is the point of a self-contained section → -- @version: gate it (15c); if it's incidental and lives in a shared/expanded definition → remove it and use a cross-version equivalent (15b).

Verification

  • 10.24 (MX_BINARY=…/10.24.19.104498): 15b passes, 0 errors, both engines.
  • 11.6.3: 15b still passes, 0 errors, both engines.
  • Proactive sweep of the doctype suite for designproperties / use building block: 03/12/29/31 gate theirs, 15c was already fixed (Fix nightly on Mendix 10.24: version-gate the 11.x-only building block in 15c #43), and *.test.mdl files aren't run by TestMxCheck_DoctypeScripts. No other 10.24 landmines remain.

🤖 Generated with Claude Code


Generated by Claude Code

The nightly matrix (10.24 / 11.6 / 11.12) failed only on 10.24:
TestMxCheck_DoctypeScripts/15b-fragment-slots-examples → CE6083 "Design property
Card style is not supported by your theme" at every cardWrap container (both
engines). `Card style` is an Atlas v3 (11.x) design property; the 10.x Atlas
theme doesn't define it.

The property sat on the shared `define fragment Card`, instantiated by every page
in the file, so a --@Version gate would have to gate the whole file and lose all
10.24 coverage of the content-slot feature 15b actually demonstrates. The design
property was incidental (12-styling covers design properties, gated 11.0+), so
drop it and keep `class: 'card'` — Atlas card styling that works on every version.

Verified: 15b passes on 10.24 AND 11.6.3 (0 errors, both engines). Also swept the
doctype suite for other ungated designproperties/building-block usage — 03/12/29/31
gate theirs, 15c was already fixed (#43), and *.test.mdl files aren't run by the
doctype test. fix-issue.md records the CE6083 case + the gate-vs-remove rule.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXnEgoc2NQP1Y2TWMCMXC4
@ako
ako merged commit 3e9a102 into main Jul 27, 2026
3 checks passed
ako pushed a commit that referenced this pull request Jul 29, 2026
…ll gaps (FINDINGS #42/#36/#23/#48/#47)

- #42 DESCRIBE WORKFLOW dropped the `with (...)` param mappings: the modelsdk read
  path built a CallMicroflowTask with only Microflow+Outcomes and never populated
  ParameterMappings, so describe→drop→exec silently lost the mapping (which nothing
  then reports). Added microflowParamMappingsFromGen and wired it into both the
  CallMicroflowTask and CallMicroflowActivity read cases; the legacy sdk/mpr parser
  already read them. Round-trip test added; verified `describe workflow` now emits
  `call microflow M.ACT_Do with (Item = '$workflowContext')`.
- #36 SEC005 lint suggested `ALTER PROJECT SECURITY STRICT MODE ON`, a statement the
  parser doesn't implement. Strict mode is Studio Pro-only — the suggestion now says
  so instead of naming an unrunnable command.
- #23 documented `create or modify association` (the idempotent form) in the
  domain-model skill: plain `create association` is not idempotent and its failure
  aborts the rest of the script.
- #48 documented `set task outcome $Task '<Outcome>'` (there is no `complete task`)
  and the other workflow task statements in write-workflows.
- #47 documented that System-module enumerations are read from the runtime, not the
  .mpr, so mxcli can't resolve them — constrain on an attribute instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXnEgoc2NQP1Y2TWMCMXC4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants