Skip to content

Improve in-component guard examples #1704

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 2 commits into from
Oct 11, 2017
Merged

Improve in-component guard examples #1704

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e8d3b19
Improve in-component guard examples
LinusBorg Aug 25, 2017
d18206d
Update navigation-guards.md
yyx990803 Oct 11, 2017
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
22 changes: 21 additions & 1 deletion docs/en/advanced/navigation-guards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,27 @@ beforeRouteEnter (to, from, next) {
}
```

You can directly access `this` inside `beforeRouteLeave`. The leave guard is usually used to prevent the user from accidentally leaving the route with unsaved edits. The navigation can be canceled by calling `next(false)`.
You can directly access `this` inside `beforeRouteEnter` and `beforeRouteLeave`, so using this callback is not necessary and therefore *not supported*:

```js
beforeRouteUpdate (to, from, next) {
this.name = to.params.name
next()
}
```

The **leave guard** is usually used to prevent the user from accidentally leaving the route with unsaved edits. The navigation can be canceled by calling `next(false)`.

```js
beforeRouteLeave (to, from , next) {
const answer = window.confirm('Do you really want to leave? you have unsaved changes!')
if (answer) {
next()
} else {
next(false)
}
}
```

### The Full Navigation Resolution Flow

Expand Down