Skip to content
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

fix(router): Ensure canceledNavigationResolution: 'computed' works … #51441

Closed
wants to merge 2 commits into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Aug 21, 2023

…on first page

Setting the page ID is currently broken for the first page because the helper method's second parameter is optional, which allowed the initally undefined page ID to be used again when the router performs its initial navigation.

fixes #50983

…on first page

Setting the page ID is currently broken for the first page because the
helper method's second parameter is optional, which allowed the initally
`undefined` page ID to be used again when the router performs its
initial navigation.

fixes angular#50983
@atscott atscott added target: patch This PR is targeted for the next patch release area: router labels Aug 21, 2023
@ngbot ngbot bot added this to the Backlog milestone Aug 21, 2023
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.

👍

packages/router/src/router.ts Outdated Show resolved Hide resolved
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Aug 21, 2023
@AndrewKushnir
Copy link
Contributor

This PR was merged into the repository by commit 96d94ad.

AndrewKushnir pushed a commit that referenced this pull request Aug 21, 2023
…on first page (#51441)

Setting the page ID is currently broken for the first page because the
helper method's second parameter is optional, which allowed the initally
`undefined` page ID to be used again when the router performs its
initial navigation.

fixes #50983

PR Close #51441
thomasturrell pushed a commit to thomasturrell/angular that referenced this pull request Aug 29, 2023
…on first page (angular#51441)

Setting the page ID is currently broken for the first page because the
helper method's second parameter is optional, which allowed the initally
`undefined` page ID to be used again when the router performs its
initial navigation.

fixes angular#50983

PR Close angular#51441
@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 Sep 21, 2023
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…on first page (angular#51441)

Setting the page ID is currently broken for the first page because the
helper method's second parameter is optional, which allowed the initally
`undefined` page ID to be used again when the router performs its
initial navigation.

fixes angular#50983

PR Close angular#51441
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.

canceledNavigationResolution: computed + canDeactivate: false results unexpected behavior
2 participants