We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This should be the better fix for #338
currently, the playground generates this code:
import _definePage_default_0 from '/Users/posva/unplugin-vue-router/playground/src/pages/index.vue?definePage&vue' import _definePage_named_1 from '/Users/posva/unplugin-vue-router/playground/src/pages/[email protected]?definePage&vue' import { _mergeRouteRecord } from 'unplugin-vue-router/runtime' export const routes = [ _mergeRouteRecord( { path: '/', name: 'home', components: { 'default': () => import('/Users/posva/unplugin-vue-router/playground/src/pages/index.vue'), 'named': () => import('/Users/posva/unplugin-vue-router/playground/src/pages/[email protected]') }, /* no children */ }, _definePage_default_0, _definePage_named_1 ), // ...
Since [email protected] doesn't have a definePage() inside it, it would be better if it was skipped completely
[email protected]
definePage()
The text was updated successfully, but these errors were encountered:
@posva Does this mean that the resulting meta will be the last route now? that is, meta _definePage_named_1 will overwrite meta _definePage_default_0
Sorry, something went wrong.
no, meta is still merged
meta
No branches or pull requests
This should be the better fix for #338
currently, the playground generates this code:
Since
[email protected]
doesn't have adefinePage()
inside it, it would be better if it was skipped completelyThe text was updated successfully, but these errors were encountered: