1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

Document router events the way they are used (#3268)

This commit is contained in:
Tim Neutkens 2017-11-11 20:54:50 +01:00 committed by GitHub
parent dc07cd1b19
commit ccaf640b47
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -474,15 +474,15 @@ This uses of the same exact parameters as in the `<Link>` component.
You can also listen to different events happening inside the Router.
Here's a list of supported events:
- `routeChangeStart(url)` - Fires when a route starts to change
- `routeChangeComplete(url)` - Fires when a route changed completely
- `routeChangeError(err, url)` - Fires when there's an error when changing routes
- `beforeHistoryChange(url)` - Fires just before changing the browser's history
- `appUpdated(nextRoute)` - Fires when switching pages and there's a new version of the app
- `onRouteChangeStart(url)` - Fires when a route starts to change
- `onRouteChangeComplete(url)` - Fires when a route changed completely
- `onRouteChangeError(err, url)` - Fires when there's an error when changing routes
- `onBeforeHistoryChange(url)` - Fires just before changing the browser's history
- `onAppUpdated(nextRoute)` - Fires when switching pages and there's a new version of the app
> Here `url` is the URL shown in the browser. If you call `Router.push(url, as)` (or similar), then the value of `url` will be `as`.
Here's how to properly listen to the router event `routeChangeStart`:
Here's how to properly listen to the router event `onRouteChangeStart`:
```js
Router.onRouteChangeStart = url => {