feat(portal-next): resolve navigation visibility with caller-then-par… - #19502
Open
konrad-krol-incubly wants to merge 1 commit into
Open
Conversation
konrad-krol-incubly
marked this pull request as ready for review
August 31, 2026 13:38
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
konrad-krol-incubly
force-pushed
the
refactor/ext-179-consolidate-nav-validation
branch
3 times, most recently
from
August 31, 2026 15:00
ab68525 to
a33434d
Compare
…ent-then-public precedence
konrad-krol-incubly
force-pushed
the
feat/ext-179-navigation-visibility-core
branch
from
August 31, 2026 15:03
ca5a013 to
68d8a58
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue
https://gravitee.atlassian.net/browse/EXT-179
Description
Removes hardcoded
PortalVisibility.PUBLICfrom every automation-api related sync service that materializes portal navigation items. Producers now inherit the parent's visibility (fallback: PUBLIC at root), so a PUBLIC child under a PRIVATE parent can no longer be materialized silently.Existing
ParentRuleis reused to validate parent-child visibility constraints.Requires follow-up PR to expose visibility property on REST API.