docs: changes for 0.7.0

Author: yyx990803

docs/en/api/go.md

@@ -28,3 +28,11 @@ Programatically navigate to a new route.
   ```
 
   For details about the `name` Object format, see [Named Routes](../named.md).
+
+  - When using the `path` format and navigating to a relative path, you can also pass in the `append: true` option, so that the relative path is always **appended** to the current path. For example:
+
+    - Going from `/a` to `b` without `append: true` will arrive at `/b`;
+
+    - Going from `/a` to `b` with `append: true` will arrive at `/a/b`.
+
+  - Both formats also accept the `replace: true` option, which makes the navigation to replace the current history entry instead of creating a new one.

docs/en/link.md

@@ -23,13 +23,37 @@
 
 #### Active Link Class
 
-Elements with `v-link` will automatically get corresponding class names when the current path matches its `v-link` URL:
+Elements with `v-link` will automatically get corresponding class names when the current path matches its `v-link` URL. The default class to be applied is `.v-link-active` and the default matching behavior is **inclusive match**. For example, an element with `v-link="/a"` will get this class applied as long as the current path starts with `/a`.
 
-- The `.v-link-active` class is applied to the element when the current path starts with the `v-link` URL. For example, an element with `v-link="/a"` will get this class as long as the current path starts with `/a`.
+It is also possible to configure the matching behavior so that the active class is only applied when the paths match exactly, using the `exact` inline option:
 
-- The `.v-link-active-exact` class is applied when the current path is an exact match of the `v-link` URL.
+``` html
+<a v-link="{ path: '/a', exact: true }"></a>
+```
+
+The active link class name can be configured with the `linkActiveClass` option when creating the router instance. It can also be overridden with the `activeClas` inline option:
+
+``` html
+<a v-link="{ path: '/a', activeClass: 'custom-active-class' }"></a>
+```
+
+#### Other Configuration Options
+
+- **replace**
+
+  A link with `replace: true` will call `router.replace()` instead of `router.go()` when clicked, so the navigation will not leave a history record.
+
+  ``` html
+  <a v-link="{ path: '/abc', replace: true }"></a>
+  ```
+
+- **append**
+
+  A relative link with `append: true` always append the relative path to the current path. For example, assuming we are navigating from `/a` to a relative link `b`, without `append: true` we will end up at `/b`, but with `append: true` we will end up at `/a/b`.
 
-The active link class name can be configured with the `linkActiveClass` option when creating the router instance. The exact match class simply appends `-exact` postfix to the provided class name.
+  ``` html
+  <a v-link="{ path: 'relative/path', append: true }"></a>
+  ```
 
 #### Additional Notes
 

docs/en/options.md

@@ -38,7 +38,7 @@ There are a number of options you can use to customize the router behavior when
 
 - default: `"v-link-active"`
 
-  Configures the class to be applied to `v-link` elements when the current path matches its URL. The base class is applied as long as the current path starts with the `v-link` URL; when the current path matches the `v-link` URL exactly, an additional class with the `-exact` postfix will also be applied,the default being `v-link-active-exact`. So if you configure the class to be `my-custom-active`, the exact match class will be `my-custom-active-exact`.
+  Configures the class to be applied to `v-link` elements when the current link is active. The matching behavior and the class can also be individually configured for each `v-link`.
 
 #### saveScrollPosition
 

docs/en/route.md

@@ -20,6 +20,10 @@ A route object exposes the following properties:
 
   The router instance that is managing this route (and its owner component).
 
+- **$route.matched**
+
+  An array containing the route configuration objects for all matched segments in the current route.
+
 ### Custom Fields
 
 In addition to the built-in properties, custom fields defined in the route config will also be merged on to the route object. For example: