Use case
The Mendix-recommended place for an app's own styling is a UI resources module: a module marked "UI resources package" and put last in App Settings → Theme → module order, so its themesource/<module>/web SCSS compiles after Atlas and wins.
With mxcli you can create the module and write its SCSS files, but you cannot:
- mark it as a UI resources module (the
IsThemeModule flag on the module), or
- place it in the theme module order (the project theme settings' module order).
mxcli syntax --json (v0.24.0) has no entry for either. So scripted app setup has to stop and ask someone to open Studio Pro. Otherwise the styles compile in the wrong order and part of the theme appears not to apply, with no error anywhere.
Proposed syntax (one option)
create module "BrandTheme" (UIResources: true);
alter module "BrandTheme" set UIResources = true;
alter settings theme set ModuleOrder = ('Atlas_Core', 'Atlas_Web_Content', 'BrandTheme');
-- or: alter settings theme move module "BrandTheme" last;describe module / describe settings would show both.
Mendix version
11.14.0 (the same settings exist in 10.x).
Use case
The Mendix-recommended place for an app's own styling is a UI resources module: a module marked "UI resources package" and put last in App Settings → Theme → module order, so its
themesource/<module>/webSCSS compiles after Atlas and wins.With mxcli you can create the module and write its SCSS files, but you cannot:
IsThemeModuleflag on the module), ormxcli syntax --json(v0.24.0) has no entry for either. So scripted app setup has to stop and ask someone to open Studio Pro. Otherwise the styles compile in the wrong order and part of the theme appears not to apply, with no error anywhere.Proposed syntax (one option)
describe module/describe settingswould show both.Mendix version
11.14.0 (the same settings exist in 10.x).