docs: use getRouteHierarchy for breadcrumbs Flow router trail#11918
Merged
Conversation
web-padawan
force-pushed
the
docs/breadcrumbs-flow-route-hierarchy
branch
from
047f97f to
3d648f2
Compare
web-padawan
force-pushed
the
docs/breadcrumbs-flow-spec-theme-variants-i18n
branch
from
aea2746 to
d82f16e
Compare
Base automatically changed from
docs/breadcrumbs-flow-spec-theme-variants-i18n
to
main
June 11, 2026 07:18
web-padawan
force-pushed
the
docs/breadcrumbs-flow-route-hierarchy
branch
from
0bfc38b to
385eb3f
Compare
web-padawan
force-pushed
the
docs/breadcrumbs-flow-route-hierarchy
branch
2 times, most recently
from
bb85465 to
1f064e3
Compare
web-padawan
force-pushed
the
docs/breadcrumbs-flow-route-hierarchy
branch
from
4e0b941 to
403bca2
Compare
Align the breadcrumbs Flow spec, API and tasks with Flow core PR #24550: build the router-mode trail on the public RouteConfiguration#getRouteHierarchy (returning RouteParentReference) and instance-free title resolution, replacing the earlier proposed RouteHierarchy walker. Refer to the Flow PR for API details rather than restating them. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
web-padawan
force-pushed
the
docs/breadcrumbs-flow-route-hierarchy
branch
from
403bca2 to
dc2d12e
Compare
|
sissbruecker
approved these changes
Jun 11, 2026
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
2 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.
Depends on #11923
Aligns the breadcrumbs Flow spec, API, and tasks with Flow core PR #24550, which ships the route-hierarchy and instance-free-title APIs the router mode needs.
RouteConfiguration#getRouteHierarchy(target, params)(returnsList<RouteParentReference>, root→current, cycle-guarded) instead of the earlier proposedRouteHierarchy.resolveAncestorswalker.@PageTitle/PageTitleGeneratorwithout instantiating views; the current view's liveHasDynamicTitleis still preferred for the last item. Ancestors resolve with theRouteParametersnarrowed to their own template.@RouteParent— now documented as shipping in PR #24550 (staticvalue()+ dynamicresolver()); removed the speculative annotation/algorithm code blocks in favour of a PR reference.@RouteParentdependency subsections collapse into one concise "Flow core: route hierarchy and titles (PR #24550)" dependency note.Discussion entries added/updated for the API change; spec bodies kept current-state-only and defer API detail to the Flow PR.
🤖 Generated with Claude Code