Skip to content

refactor: rename RouteParentReference to RouteReference#24602

Merged
mshabarov merged 2 commits into
mainfrom
refactor/rename-route-reference
Jun 15, 2026
Merged

refactor: rename RouteParentReference to RouteReference#24602
mshabarov merged 2 commits into
mainfrom
refactor/rename-route-reference

Conversation

@totally-not-ai

Copy link
Copy Markdown
Contributor

The record only carries a navigation target and its route parameters, so
it identifies any route regardless of whether the route has a logical
parent. The parent-specific name was misleading; rename it to
RouteReference. RouteParentResolver and the route hierarchy APIs keep
returning it.

The record only carries a navigation target and its route parameters, so
it identifies any route regardless of whether the route has a logical
parent. The parent-specific name was misleading; rename it to
RouteReference. RouteParentResolver and the route hierarchy APIs keep
returning it.
@github-actions

github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown

Test Results

 1 451 files  ±0   1 451 suites  ±0   1h 22m 17s ⏱️ +36s
10 249 tests ±0  10 181 ✅ ±0  68 💤 ±0  0 ❌ ±0 
10 721 runs  ±0  10 652 ✅ ±0  69 💤 ±0  0 ❌ ±0 

Results for commit 4a6637e. ± Comparison against base commit 3a51a38.

♻️ This comment has been updated with latest results.

mshabarov
mshabarov previously approved these changes Jun 15, 2026
@sonarqubecloud

Copy link
Copy Markdown

@mshabarov mshabarov added this pull request to the merge queue Jun 15, 2026
Merged via the queue into main with commit 8aa3f9e Jun 15, 2026
34 checks passed
@mshabarov mshabarov deleted the refactor/rename-route-reference branch June 15, 2026 12:18
Artur- pushed a commit that referenced this pull request Jun 15, 2026
… 25.2) (#24630)

This PR cherry-picks changes from the original PR #24602 to branch 25.2.
---
#### Original PR description
> The record only carries a navigation target and its route parameters,
so
> it identifies any route regardless of whether the route has a logical
> parent. The parent-specific name was misleading; rename it to
> RouteReference. RouteParentResolver and the route hierarchy APIs keep
> returning it.
>

Co-authored-by: totally-not-ai[bot] <290682512+totally-not-ai[bot]@users.noreply.github.com>
Co-authored-by: mikhail <mikhail@vaadin.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants