From 4c341ebb2dd43268c200389fa01b378e02e2f5e8 Mon Sep 17 00:00:00 2001 From: Eduardo San Martin Morote Date: Wed, 8 Nov 2023 14:11:12 +0100 Subject: [PATCH] docs: link typo --- packages/docs/guide/migration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/guide/migration/index.md b/packages/docs/guide/migration/index.md index c4bcbd62..f339bea4 100644 --- a/packages/docs/guide/migration/index.md +++ b/packages/docs/guide/migration/index.md @@ -437,7 +437,7 @@ Decoded values in `params`, `query`, and `hash` are now consistent no matter whe Given any [normalized route location](/api/interfaces/RouteLocationNormalized.md): - Values in `path`, `fullPath` are not decoded anymore. They will appear as provided by the browser (most browsers provide them encoded). e.g. directly writing on the address bar `https://example.com/hello world` will yield the encoded version: `https://example.com/hello%20world` and both `path` and `fullPath` will be `/hello%20world`. -- `hash` is now decoded, that way it can be copied over: `router.push({ hash: $route.hash })` and be used directly in [scrollBehavior](/api/interfaces/RouterOptions.mdscrollBehavior)'s `el` option. +- `hash` is now decoded, that way it can be copied over: `router.push({ hash: $route.hash })` and be used directly in [scrollBehavior](/api/interfaces/RouterOptions.md#scrollBehavior)'s `el` option. - When using `push`, `resolve`, and `replace` and providing a `string` location or a `path` property in an object, **it must be encoded** (like in the previous version). On the other hand, `params`, `query` and `hash` must be provided in its unencoded version. - The slash character (`/`) is now properly decoded inside `params` while still producing an encoded version on the URL: `%2F`. -- 2.39.5