-
Notifications
You must be signed in to change notification settings - Fork 27k
feat(router): add a currentNavigation signal to the Router service. #63011
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
feb070a to
9307c27
Compare
32f84e5 to
78f36a9
Compare
thePunderWoman
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, size-tracking
|
We should run a TGP for this since it broke some targets last time around. |
packages/core/schematics/migrations/router-current-navigation/README.md
Outdated
Show resolved
Hide resolved
This new signal property is convenient to derive a `isNavigating` state. `isNavigating = computed(() => !!this.router.currentNavigation())` DEPRECATED: The Router.getCurrentNavigation method is deprecated. Use the Router.currentNavigation signal instead. fixes angular#62958
78f36a9 to
e650fb4
Compare
|
This PR was merged into the repository by commit 687c374. The changes were merged into the following branches: main |
|
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. |
This #62971 re-opened
This new signal property is convenient to derive a
isNavigatingstate.isNavigating = computed(() => !!this.router.currentNavigation())DEPRECATED: The Router.getCurrentNavigation method is deprecated. Use the Router.currentNavigation signal instead.
fixes #62958