-
Notifications
You must be signed in to change notification settings - Fork 26.2k
test(router): Add tests for initialNavigation: enabledBlocking #45733
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
df89d9e
to
fb9703e
Compare
346ed10
to
8c06d9d
Compare
8c06d9d
to
0f90237
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.
👍
0f90237
to
ebe14d9
Compare
Adds additional tests to verify `enabledBlocking` functionality. The initial attempt to fix angular#44355 would have broken the scenario where a new navigation cancels the initial navigation. We also cannot rely on `NavigationError` like the example workaround in that issue report is doing because there won't be one if a guard simply rejects the initial nav (angular#16211).
ebe14d9
to
44a91f1
Compare
There are merge issues with |
This PR was merged into the repository by commit e92799c. |
Adds additional tests to verify `enabledBlocking` functionality. The initial attempt to fix #44355 would have broken the scenario where a new navigation cancels the initial navigation. We also cannot rely on `NavigationError` like the example workaround in that issue report is doing because there won't be one if a guard simply rejects the initial nav (#16211). PR Close #45733
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. |
Adds additional tests to verify
enabledBlocking
functionality. Theinitial attempt to fix #44355 would have broken the scenario where a new
navigation cancels the initial navigation. We also cannot rely on
NavigationError
like the example workaround in that issue report isdoing because there won't be one if a guard simply rejects
the initial nav (#16211).