-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
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
aliases with i18n support #1298
Comments
Thanks. This is different because aliases allow several different names for the same page. Aliases are actually generated using i18n, but you don't have any control over them. For example, if the page 'main.vue' contains:
then /posts, /articles, /blog will all be generated with the main.vue page content, but unfortunately you do not have control over i18n, e.g.,
is ignored even though /blog is generated for all the locales. |
What I really need is this:
|
I think my proposed change in #1281 would allow for such functionality. I'm using it in production for a couple sites I needed to be able to define the routes manually since the module didn't knew how to handle those cases. We would need to make sure my changes don't break core functionality (pretty sure I didn't account for all scenarios this module handles) but I wanna say it wouldn't be too hard to also add support for this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
hello. how do i do this using i18n?
(feature from https://github.com/nuxt-community/router-extras-module)
i want to be able to configure their i18n routes:
The text was updated successfully, but these errors were encountered: