-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Combine recognize and apply redirects #49163
Conversation
9f3d0c4
to
e53bc2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@atscott I've looked through the change and I'd like to ask if we can pair to view it together, so I can better understand the context. Thank you.
4ba3d6d
to
627d211
Compare
627d211
to
f49bbd3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed-for: size-tracking
This PR was merged into the repository by commit 1600687. |
…gating (angular#49163)" This reverts commit 1600687.
When navigating in the Router, the current approach does the redirects and the creation of the `RouterStateSnapshot` in two separate steps (applyRedirects and recognize). These two steps duplicate the route matching logic, resulting in user code on routes being executing twice (custom `UrlMatcher` and `canMatch` guards). This also duplicates the complex matching logic in two places, which increases the bundle size and maintenance burden. This commit combines the `applyRedirects` and `recognize` steps into a single matching algorithm. fixes angular#26081
f49bbd3
to
ea1a12d
Compare
Re-merging. I've confirmed this was an issue with the internal route configuration. |
This PR was merged into the repository by commit 3c7e637. |
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. |
No description provided.