| editLink |
|---|
API Documentation / RouteRecordMultipleViews
Route Record defining multiple named components with the components option.
-
↳
RouteRecordMultipleViews
• Optional alias: string | string[]
Aliases for the record. Allows defining extra paths that will behave like a
copy of the record. Allows having paths shorthands like /users/:id and
/u/:id. All alias and path values must share the same params.
• Optional beforeEnter: NavigationGuardWithThis<undefined> | NavigationGuardWithThis<undefined>[]
Before Enter guard specific to this record. Note beforeEnter has no
effect if the record has a redirect property.
• Optional children: undefined
Array of nested routes.
• Optional component: undefined
• components: Record<string, RawRouteComponent>
Components to display when the URL matches this route. Allow using named views.
• Optional end: boolean
Should the RegExp match until the end by appending a $ to it.
Default Value
true
• Optional meta: RouteMeta
Arbitrary data attached to the record.
• Optional name: RouteRecordNameGeneric
Name for the route record. Must be unique.
• path: string
Path of the record. Should start with / unless the record is the child of
another record.
Example
`/users/:id` matches `/users/1` as well as `/users/posva`.• Optional props: boolean | Record<string, _RouteRecordProps>
Allow passing down params as props to the component rendered by
router-view. Should be an object with the same keys as components or a
boolean to be applied to every component.
• Optional redirect: undefined
Where to redirect if the route is directly matched. The redirection happens before any navigation guard and triggers a new navigation with the new target location.
• Optional sensitive: boolean
Makes the RegExp case-sensitive.
Default Value
false
• Optional strict: boolean
Whether to disallow a trailing slash or not.
Default Value
false