You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would make more sense to add an option to allow the plugin to read (parse with babel) from a router.ts file or routes.ts. The user would need to declare the routes with a macro defineTypedRoutes() that would get stripped out from the router file but would allow to read the path and names (when existing) from the routes array and create the files. The current implementation does require users to have most of the routes named. It could also rewrite the files to add names but this starts to become too much. I think it's better to require users to have all useful routes named (it's okay to have a route without component or components without a name)
zhangmo8
added a commit
to zhangmo8/unplugin-vue-router
that referenced
this issue
Aug 5, 2024
# This is the 1st commit message:
chore: resolve conflicts
# This is the commit message posva#2:
fix: fix the vue-loader error
# This is the commit message posva#3:
fix: setup return route
# This is the commit message posva#4:
fix: lint fix
# This is the commit message posva#5:
Update examples/webpack/shims-vue.d.ts
Co-authored-by: Eduardo San Martin Morote <[email protected]>
# This is the commit message posva#6:
chore: update webpack deps & lock file
# This is the commit message posva#7:
chore: update webpack deps & lock file
Is it possible to create a small script that takes a routes array and move the files around? or is it too much work
Maybe, it's more interesting to generate the types from a file that exposes the routes array in js or ts and parse it
The text was updated successfully, but these errors were encountered: