Skip to content

Doc EN: navigation-guards.md: minor adjustements #1600

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 14, 2017
Merged

Doc EN: navigation-guards.md: minor adjustements #1600

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions docs/en/advanced/navigation-guards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
},
Expand Down Expand Up @@ -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.
Expand Down