From 72359a76e3b798e9286f2e144563e9e18e469236 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9A=D1=80=D0=B0=D1=81=D0=B8=D0=BC=D0=B8=D1=80=20=D0=91?= =?UTF-8?q?=D0=B5=D1=80=D0=BE=D0=B2?= Date: Sat, 4 Mar 2017 23:38:34 +0100 Subject: [PATCH] Remove an obsolete line (#1681) --- docs/route.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/route.md b/docs/route.md index 1ecb8d62..65e9a600 100644 --- a/docs/route.md +++ b/docs/route.md @@ -257,8 +257,6 @@ In the example above, we defined a route `/edit/:id`. This creates a dynamic rou It's possible to have multiple arguments in a route, for example `/edit/:projectID/:userID` would yield the properties `projectID` and `userID` on the component's vnode attributes object. -In addition to routing parameters, the `attrs` object also includes a `path` property that contains the current route path, and a `route` property that contains the matched routed. - #### Key parameter When a user navigates from a parameterized route to the same route with a different parameter (e.g. going from `/page/1` to `/page/2` given a route `/page/:id`, the component would not be recreated from scratch since both routes resolve to the same component, and thus result in a virtual dom in-place diff. This has the side-effect of triggering the `onupdate` hook, rather than `oninit`/`oncreate`. However, it's relatively common for a developer to want to synchronize the recreation of the component to the route change event.