Enable nested navigation templating. #240
Merged
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.
Jira: https://issues.redhat.com/browse/RHCLOUD-36560
The Jira has links to docs and detailed explanations.
TLDR
A small number of UI modules are injecting navigation items into navigation segments that are not owned by the UI module itself. We need a templating mechanism that allows navigation segments to be injected across different modules.
Trying to do that with some paths/ordering attributes will result in many conflicts and complexity. Allowing explicit templating should make the code stable and configuration easier to understand for developers.