-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(router): Apply named outlets to children of empty paths not appearing in the URL #51292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…g in the URL Empty path routes are effectively 'passthrough' routes that do not appear in the URL. When these exist in the route tree, we do not want to apply named outlet commands to that tree location. Instead, we skip past this location in the tree, effectively squashing/removing this passthrough route from the tree. fixes angular#50356
|
caretaker note: probably a good idea to merge and sync this one on its own. |
|
This PR was merged into the repository by commit 4e22a39. |
…g in the URL (#51292) Empty path routes are effectively 'passthrough' routes that do not appear in the URL. When these exist in the route tree, we do not want to apply named outlet commands to that tree location. Instead, we skip past this location in the tree, effectively squashing/removing this passthrough route from the tree. fixes #50356 PR Close #51292
|
@atscott it seems the issue is still there...😭 Updated to 16.2.1 and still cannot use the aux outlet |
|
@atscott So on the page we have a lot of <a
[routerLink]="[{
outlets: { '[right-drawer][1]': [ 'transaction', { id: row.id } ] }
}]"
>link</a>Upon navigation to the aux route, all the hrefs Somehow |
|
@Niaro Please provide a reproduction |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…g in the URL (angular#51292) Empty path routes are effectively 'passthrough' routes that do not appear in the URL. When these exist in the route tree, we do not want to apply named outlet commands to that tree location. Instead, we skip past this location in the tree, effectively squashing/removing this passthrough route from the tree. fixes angular#50356 PR Close angular#51292
Empty path routes are effectively 'passthrough' routes that do not appear in the URL. When these exist in the route tree, we do not want to apply named outlet commands to that tree location. Instead, we skip past this location in the tree, effectively squashing/removing this passthrough route from the tree.
fixes #50356