Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@MeAkib
Copy link
Contributor

@MeAkib MeAkib commented Aug 30, 2025

Fixed: #63490

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number:
#63490

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@AleksanderBodurri
Copy link
Member

@MeAkib Thanks for opening this, will take a look today 🙏

@AleksanderBodurri
Copy link
Member

Hi @MeAkib, after reviewing I think the correct way to solve this problem is to make it more clear to the user that the "Root" of the router is not a route config that the user is providing. Something like this here #63978

Alternatively we could remove the root entirely and have the initial routes in an application all be their own distinct trees in the graph.

@JeanMeche
Copy link
Member

We'll pick up the fix from there. Thanks for the suggestion though.

@JeanMeche JeanMeche closed this Oct 9, 2025
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.

All routes show as active when on homepage in DevTools

3 participants