aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgdennie2013-09-22 11:56:25 -0400
committerPete Bacon Darwin2013-09-25 22:30:10 +0100
commit3c4460b513ed25b32b1b1fa164e2664f1d502ee5 (patch)
tree983be089a6602785b4aa0238a2d376deb64576e6
parenta98931de0efe26ccc3462d0e88fdc4439aa15389 (diff)
downloadangular.js-3c4460b513ed25b32b1b1fa164e2664f1d502ee5.tar.bz2
docs(guide/$location): provide a title for section about `replace()`
Closes #4104
-rw-r--r--docs/content/guide/dev_guide.services.$location.ngdoc2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/content/guide/dev_guide.services.$location.ngdoc b/docs/content/guide/dev_guide.services.$location.ngdoc
index b0178ecf..1720d473 100644
--- a/docs/content/guide/dev_guide.services.$location.ngdoc
+++ b/docs/content/guide/dev_guide.services.$location.ngdoc
@@ -121,6 +121,8 @@ All of the setter methods return the same `$location` object to allow chaining.
change multiple segments in one go, chain setters like this:
<pre>$location.path('/newValue').search({key: value});</pre>
+## Replace method
+
There is a special `replace` method which can be used to tell the $location service that the next
time the $location service is synced with the browser, the last history record should be replaced
instead of creating a new one. This is useful when you want to implement redirection, which would