BMAD-METHOD/tools/cli/lib
Nikita Levyankov 32b104b4bc fix: handle array-wrapped 'all' value for modules
After wrapping profile string values in arrays in options-parser, the modules handling in ui.js was still only checking for string 'all', not array ['all']. This would break profiles with `modules: 'all'`.

Added checks for both cases:
- String: `options.modules === 'all'` (original case)
- Array: `options.modules.includes('all')` (new case after wrapping)

Now modules handling is consistent with agents/workflows filtering which already used `.includes('all')`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-18 12:39:07 +02:00
..
agent fixed issue with agent customization application, now all fields are customized form the custom yaml. also added a recompile agents menu item 2025-12-17 17:58:37 +08:00
activation-builder.js folder rename from .bmad to _bmad 2025-12-13 16:22:34 +08:00
agent-analyzer.js we only need one yaml lib 2025-12-13 18:35:07 +08:00
agent-party-generator.js _cfg -> _config 2025-12-13 19:41:09 +08:00
cli-utils.js custom install module cached 2025-12-07 20:46:09 -06:00
config.js we only need one yaml lib 2025-12-13 18:35:07 +08:00
file-ops.js feat: v6.0.0-alpha.0 - the future is now 2025-09-28 23:17:07 -05:00
platform-codes.js we only need one yaml lib 2025-12-13 18:35:07 +08:00
project-root.js feat: v6.0.0-alpha.0 - the future is now 2025-09-28 23:17:07 -05:00
ui.js fix: handle array-wrapped 'all' value for modules 2025-12-18 12:39:07 +02:00
xml-handler.js folder rename from .bmad to _bmad 2025-12-13 16:22:34 +08:00
xml-to-markdown.js feat: v6.0.0-alpha.0 - the future is now 2025-09-28 23:17:07 -05:00
yaml-format.js we only need one yaml lib 2025-12-13 18:35:07 +08:00
yaml-xml-builder.js _cfg -> _config 2025-12-13 19:41:09 +08:00