vue-router

This PR enhances and expands the existing guide for Route Meta Fields () in the Advanced Guide section. Changes include: 1. Improved overall structure, clarity, and explanations of the object and the use of the array for nested routes. 2. Added a crucial, second real-world use case: Setting dynamic page titles** using the global hook. This update provides a more comprehensive and practical guide for developers using metadata in the Vue 2 version of Vue Router.

What problem does this feature solve? Allow less hierarchical and shorter urls for nested routes and general wide usecase flexibility. Due to limitations of simple pattern matching the example from https://router.vuejs.org/guide/essentials/nested-routes.html require hierarchical urls for nesting routes and router-views e.g. and , routes without a common parent-path can't be nested. Example: Let's say we want a tabbed overview page with different topics like this The routes would look like this The pattern matching dictates hierarchical urls like above , , . Shorter urls like , , can't be achieved (while still keeping the overview page with the tabs). With custom matcher (functions) that would be possible. This is especially important when migrating from other frameworks, where the url structure can't be changed for SEO and other reasons. What does the proposed API look like? For the example above that could look like this: This is similar to the how Angular handles it: https://angular.io/api/router/UrlMatcher

Hello Vue Router team, I have encountered an issue with the vue-router.global.js build in the dist folder. Specifically, the isSameRouteLocationParamsValue function inside the globally distributed file contains the optional chaining (?.) operator, which is not transpiled to ES5. This could cause compatibility issues in environments that don’t support optional chaining, such as older browsers. Here’s the snippet from the distributed vue-router.global.js file: