93f6547554
Per augment review on #2348: loadExistingConfig stored any truthy yaml.parse result (including scalars like '42'), which would later crash _hoistCoreKeysFromLegacyModuleConfigs at \`key in cfg\` with "Cannot use 'in' operator to search for ... in 42". - loadExistingConfig: only keep parses that are plain objects (not scalars or arrays). A corrupt config.yaml is now treated the same as a parse error — skipped, not crashed-on. - _hoistCoreKeysFromLegacyModuleConfigs: belt-and-suspenders type guards on _existingConfig.core (in case it's populated by some other path) and on each module cfg in the loop. - Test Suite 43 adds 2 assertions covering a scalar core/config.yaml: loadExistingConfig must not crash, and bmm.project_name must still hoist into a clean core bucket. |
||
|---|---|---|
| .. | ||
| channel-plan.js | ||
| channel-resolver.js | ||
| community-manager.js | ||
| custom-module-manager.js | ||
| external-manager.js | ||
| official-modules.js | ||
| plugin-resolver.js | ||
| registry-client.js | ||
| registry-fallback.yaml | ||
| version-resolver.js | ||