Skip to content

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

Closed
wants to merge 1 commit into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Apr 22, 2022

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).

@atscott atscott added area: router target: patch This PR is targeted for the next patch release labels Apr 22, 2022
@atscott atscott requested a review from CaerusKaru April 22, 2022 23:12
@ngbot ngbot bot modified the milestone: Backlog Apr 22, 2022
@atscott atscott force-pushed the additionalinitialnavtests branch from df89d9e to fb9703e Compare May 2, 2022 16:04
@atscott atscott requested a review from AndrewKushnir May 3, 2022 22:46
@atscott atscott force-pushed the additionalinitialnavtests branch 2 times, most recently from 346ed10 to 8c06d9d Compare May 3, 2022 22:49
@atscott atscott force-pushed the additionalinitialnavtests branch from 8c06d9d to 0f90237 Compare May 17, 2022 20:31
Copy link
Contributor

@AndrewKushnir AndrewKushnir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@atscott atscott force-pushed the additionalinitialnavtests branch from 0f90237 to ebe14d9 Compare May 17, 2022 20:48
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).
@atscott atscott force-pushed the additionalinitialnavtests branch from ebe14d9 to 44a91f1 Compare May 17, 2022 20:49
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label May 17, 2022
@atscott atscott removed the request for review from CaerusKaru May 17, 2022 20:50
@jessicajaniuk jessicajaniuk added target: rc This PR is targeted for the next release-candidate and removed target: patch This PR is targeted for the next patch release labels May 18, 2022
@jessicajaniuk
Copy link
Contributor

There are merge issues with 13.3.x. Switching to target: rc.

@jessicajaniuk
Copy link
Contributor

This PR was merged into the repository by commit e92799c.

jessicajaniuk pushed a commit that referenced this pull request May 18, 2022
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
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: router target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Router initializer never completes if initial navigation fails
3 participants