From 95dff2de9d5be22ab722ae9ba4fa0664f2d2656d Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Thu, 13 Jul 2017 17:34:43 +0200 Subject: [PATCH] Minor adjustements. Signed-off-by: Bruno Lesieur --- docs/en/advanced/navigation-guards.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/en/advanced/navigation-guards.md b/docs/en/advanced/navigation-guards.md index 8ff4cc730..a9efe15a2 100644 --- a/docs/en/advanced/navigation-guards.md +++ b/docs/en/advanced/navigation-guards.md @@ -91,8 +91,8 @@ const Foo = { beforeRouteUpdate (to, from, next) { // called when the route that renders this component has changed, // but this component is reused in the new route. - // For example, for a route with dynamic params /foo/:id, when we - // navigate between /foo/1 and /foo/2, the same Foo component instance + // For example, for a route with dynamic params `/foo/:id`, when we + // navigate between `/foo/1` and `/foo/2`, the same `Foo` component instance // will be reused, and this hook will be called when that happens. // has access to `this` component instance. }, @@ -120,14 +120,14 @@ You can directly access `this` inside `beforeRouteLeave`. The leave guard is usu ### The Full Navigation Resolution Flow -1. Navigation triggered -2. Call leave guards in deactivated components -3. Call global `beforeEach` guards -4. Call `beforeRouteUpdate` guards in reused components (2.2+) -5. Call `beforeEnter` in route configs -6. Resolve async route components -7. Call `beforeRouteEnter` in activated components -8. Call global `beforeResolve` guards (2.5+) +1. Navigation triggered. +2. Call leave guards in deactivated components. +3. Call global `beforeEach` guards. +4. Call `beforeRouteUpdate` guards in reused components (2.2+). +5. Call `beforeEnter` in route configs. +6. Resolve async route components. +7. Call `beforeRouteEnter` in activated components. +8. Call global `beforeResolve` guards (2.5+). 9. Navigation confirmed. 10. Call global `afterEach` hooks. 11. DOM updates triggered.