-
Notifications
You must be signed in to change notification settings - Fork 27k
feat(router): Add new NavigationCancellation code and events for igno… #48024
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
e7305b6 to
6ca166b
Compare
bc33beb to
293b229
Compare
293b229 to
9307918
Compare
jessicajaniuk
left a comment
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: public-api
AndrewKushnir
left a comment
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: public-api, fw-router
3d4c40f to
8f398ee
Compare
8f398ee to
420318c
Compare
420318c to
fbcfe7e
Compare
The Router currently silently ignores navigations for two reasons: 1. By default, same URL navigations are ignored. When this situation is encountered, the navigation is ignored without any events 2. A `UrlHandlingStrategy` may ignore some URLs. For situations when the strategy returns `false` for `shouldProcessUrl`, the Router silently ignores the URL and updates its internal state without running matching, guards, or resolver logic. This commit adds new `NavigationSkipped` events for the above two situations.
fbcfe7e to
ea52596
Compare
|
This PR was merged into the repository by commit 73f03ad. |
|
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. |
…angular#48024) The Router currently silently ignores navigations for two reasons: 1. By default, same URL navigations are ignored. When this situation is encountered, the navigation is ignored without any events 2. A `UrlHandlingStrategy` may ignore some URLs. For situations when the strategy returns `false` for `shouldProcessUrl`, the Router silently ignores the URL and updates its internal state without running matching, guards, or resolver logic. This commit adds new `NavigationSkipped` events for the above two situations. PR Close angular#48024
…red navigations
The Router currently silently ignores navigations for two reasons:
UrlHandlingStrategymay ignore some URLs. For situations when the strategy returnsfalseforshouldProcessUrl, the Router silently ignores the URL and updates its internal state without running matching, guards, or resolver logic.This commit adds new
NavigationCancellationcodes andNavigationCancelevents for the above two situations.