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
Heyho! First of all: Thanks for marking this module 🙏
I'm currently building my companies page with "German" (de) as the default language. So far so good. The only thing that annoys me a bit is that the keys in the routes object should match the base routes from Nuxt. I think it'd be better to use them as custom/general keys.
Short and meaningful keys, and clear routing that doesn't depend on the actual components.
But I guess that's a lot of work because you'd need to find out the component for each custom route as well. I'm not sure if that's even possible (except you set it in the config)
This question is available on Nuxt.js community (#c5)
The text was updated successfully, but these errors were encountered:
TheAlexLichter
changed the title
Feature request: Route key for default language as well
Feature request: Custom route keys
Feb 10, 2018
Using Nuxt's base routes feels like the safest thing to do for this feature to prevent any confusions.
Ideally, I'd like to have an option to configure custom routes right in the .vue files rather than putting them all in a config file but I'm lacking time to give it a try atm.
Heyho! First of all: Thanks for marking this module 🙏
I'm currently building my companies page with "German" (de) as the default language. So far so good. The only thing that annoys me a bit is that the keys in the routes object should match the base routes from Nuxt. I think it'd be better to use them as custom/general keys.
Currently, my route file would look like this:
It's a bit annoying because I can't keep the route keys short and often I need to "escape" them with quotes (because of the hyphens).
The best case for the routes file would be
Short and meaningful keys, and clear routing that doesn't depend on the actual components.
But I guess that's a lot of work because you'd need to find out the component for each custom route as well. I'm not sure if that's even possible (except you set it in the config)
The text was updated successfully, but these errors were encountered: