This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Something along the lines of reloadOnPathParams in ngRoute #7925
Milestone
Comments
This was referenced Jan 3, 2017
Closed
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Jan 3, 2017
Enables users to specify that a particular route should not be reloaded after a URL change (including a change in `$location.path()`), if the new URL maps to the same route. The default behavior is still to always load the matched route when any part of the URL changes. Related to angular#1699, angular#5860, angular#14999 (potentially closing the first two). Fixes angular#7925
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
May 23, 2018
Enables users to specify that a particular route should not be reloaded after a URL change (including a change in `$location.path()`), if the new URL maps to the same route. The default behavior is still to always load the matched route when any part of the URL changes. Related to angular#1699, angular#5860, angular#14999 (potentially closing the first two). Fixes angular#7925
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
May 26, 2018
Enables users to specify that a particular route should not be reloaded after a URL change (including a change in `$location.path()`), if the new URL maps to the same route. The default behavior is still to always load the matched route when any part of the URL changes. Related to angular#1699, angular#5860, angular#14999 (potentially closing the first two). Fixes angular#7925
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Jun 7, 2018
Enables users to specify that a particular route should not be reloaded after a URL change (including a change in `$location.path()`), if the new URL maps to the same route. The default behavior is still to always load the matched route when any part of the URL changes. Related to angular#1699, angular#5860, angular#14999 (potentially closing the first two). Fixes angular#7925
gkalpak
added a commit
that referenced
this issue
Jun 8, 2018
Enables users to specify that a particular route should not be reloaded after a URL change (including a change in `$location.path()`), if the new URL maps to the same route. The default behavior is still to always load the matched route when any part of the URL changes. Related to #1699, #5860, #14999 (potentially closing the first two). Fixes #7925 Closes #15002
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to have an option on a route to only reload the view when path params change, much like
reloadOnSearchonly reloads the view when$location.search()changes.E.g.: If route
/foo/:idhasreloadOnPathParams = falseset, then moving from/foo/id1to/foo/id2would only broadcast a$routeUpdateevent, and not reload the view and re-instanciate the controller.The text was updated successfully, but these errors were encountered: