Adds categoryMappings array to config from json file #5236
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
cmiqueo
requested review from
gmirijan,
jedjedjedM,
sheridansunier and
shkhan91
cmiqueo
added
caas-configurator
Contributor
|
This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR. |
sanrai
approved these changes
Dec 10, 2025
sheridansunier
approved these changes
Dec 11, 2025
cmiqueo
added
Ready for Stage
and removed
trivial
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces support for a new categoryMappings field within the Milo JSON configuration. The goal is to provide more flexible and granular control over category-to-template mappings without requiring code changes.
What’s Changed
Added categoryMappings support in the CaaS Collection Configurator.
Updated logic to read category mapping rules from JSON instead of relying on hard-coded behavior.
Ensured backward compatibility when categoryMappings is absent.
Minor cleanup and structural alignment with existing config parsing.
Why This Is Needed
Some page types require custom category logic that cannot currently be expressed through the existing config. Allowing mappings to be defined in milo.json gives authors and integrators more control while reducing engineering overhead.
How It Works
The JSON config may now include a categoryMappings array.
Each mapping defines a category key and the corresponding template or behavior.
If categoryMappings is not provided, the system falls back to default behavior.
Testing
Verified that pages load expected templates when categoryMappings is present.
Confirmed that existing pages behave unchanged when the field is omitted.
Manually tested with multiple mapping configurations to verify precedence and fallback logic.
Resolves: MWPW-185006
Test URLs: