feat(router): Add ability to override onSameUrlNavigation default per-navigation#48050
feat(router): Add ability to override onSameUrlNavigation default per-navigation#48050atscott wants to merge 1 commit intoangular:mainfrom
onSameUrlNavigation default per-navigation#48050Conversation
|
CI is failing with circular deps, needs cleanup: https://app.circleci.com/pipelines/github/angular/angular/53072/workflows/40bddedb-89ad-4ae2-a6eb-fa9432f216b2/jobs/1254185 |
4b98388 to
9f0246d
Compare
9f0246d to
7186653
Compare
AndrewKushnir
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api, fw-router
dylhunn
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
|
merge assistance: pullapprove seems to be stuck |
|
@atscott Would you be able to rebase this? |
7186653 to
d56c453
Compare
d56c453 to
c942e69
Compare
…er-navigation The router providers a configurable `onSameUrlNavigation` value that allows developers to configure whether navigations to the same URL as the current one should be processed or ignored. However, this only acts as a default value and there isn't an API for easily overriding this for a single navigation. Instead, developers are forced to update the value of the property on the router instance and remember to reset it. This feature fills a small gap in the Router APIs that enables developers to accomplish the task of force reloading a bit easier. Lengthy discussion about this here: angular#21115
c942e69 to
74b6631
Compare
|
This PR was merged into the repository by commit 332461b. |
|
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. |
…er-navigation (angular#48050) The router providers a configurable `onSameUrlNavigation` value that allows developers to configure whether navigations to the same URL as the current one should be processed or ignored. However, this only acts as a default value and there isn't an API for easily overriding this for a single navigation. Instead, developers are forced to update the value of the property on the router instance and remember to reset it. This feature fills a small gap in the Router APIs that enables developers to accomplish the task of force reloading a bit easier. Lengthy discussion about this here: angular#21115 PR Close angular#48050
The router providers a configurable
onSameUrlNavigationvalue that allows developers to configure whether navigations to the same URL as the current one should be processed or ignored. However, this only acts as a default value and there isn't an API for easily overriding this for a single navigation. Instead, developers are forced to update the value of the property on the router instance and remember to reset it.This feature fills a small gap in the Router APIs that enables developers to accomplish the task of force reloading a bit easier.
Lengthy discussion about this here: #21115