Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Comments

Close side panel

fix(router): RouterTestingHarness should throw if a component is ex…#52357

Closed
atscott wants to merge 1 commit intoangular:mainangular/angular:mainfrom
atscott:testingharnessnullerroratscott/angular:testingharnessnullerrorCopy head branch name to clipboard
Closed

fix(router): RouterTestingHarness should throw if a component is ex…#52357
atscott wants to merge 1 commit intoangular:mainangular/angular:mainfrom
atscott:testingharnessnullerroratscott/angular:testingharnessnullerrorCopy head branch name to clipboard

Conversation

@atscott
Copy link
Contributor

@atscott atscott commented Oct 24, 2023

…pected but navigation fails

The RouterTestingHarness should throw an error if the call to navigateByUrl expects a component to be activated but the navigation failed.

fixes #52344

…pected but navigation fails

The `RouterTestingHarness` should throw an error if the call to `navigateByUrl`
expects a component to be activated but the navigation failed.

fixes angular#52344
@atscott atscott added the target: patch This PR is targeted for the next patch release label Oct 24, 2023
@atscott atscott requested a review from AndrewKushnir October 24, 2023 19:54
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Oct 24, 2023
@ngbot ngbot bot added this to the Backlog milestone Oct 25, 2023
@dylhunn
Copy link
Contributor

dylhunn commented Oct 25, 2023

This PR was merged into the repository by commit 0037c21.

dylhunn pushed a commit that referenced this pull request Oct 25, 2023
…pected but navigation fails (#52357)

The `RouterTestingHarness` should throw an error if the call to `navigateByUrl`
expects a component to be activated but the navigation failed.

fixes #52344

PR Close #52357
dylhunn pushed a commit that referenced this pull request Oct 25, 2023
…pected but navigation fails (#52357)

The `RouterTestingHarness` should throw an error if the call to `navigateByUrl`
expects a component to be activated but the navigation failed.

fixes #52344

PR Close #52357
@dylhunn dylhunn closed this in 0037c21 Oct 25, 2023
@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 Nov 25, 2023
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…pected but navigation fails (angular#52357)

The `RouterTestingHarness` should throw an error if the call to `navigateByUrl`
expects a component to be activated but the navigation failed.

fixes angular#52344

PR Close angular#52357
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: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RouterTestingHarness.navigateByUrl does not throw error if navigation is cancelled when the required routed component type is specified

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.