[Feature Request] Allow path to be a function about router-extras-module HOT 3 CLOSED

Hey,
Do you generate two different website for two language? Can't you create alias for other languages?

from router-extras-module.

@farnabaz

Yes - depending on the locale passed to nuxt generate (and in turn, nuxt.config.js) , it'll fetch the translation during asyncData() calls.
So if i run something like export locale=fr; npm run generate, the asyncData functions will fetch fr.json for that page being generated.

I could create an alias - but then that would mean each site gets the other aliases as well.

So if i do something like

<router>
 {
    path: '/about',      // EN
    alias: [      
      '/acerca',           // ES
      '/a-propos'        // FR
    ]
 }
</router>

And i have my site setup like:

example.com,
es.example.com,
fr.example.com

Then,
fr.example.com/about would exist,
example.com/a-propos would exist,
etc.

I do realize there's an i18n module - but it really is so heavy to do something like this - especially on statically generated sites where it loads all locale translations into the build

from router-extras-module.

I see, You can use Page validation and implement your logic.

export default {
    validate ({ store, route }) {
        if (store.state.locale === "en" && route.path != "/about") {
            return false
        }
        // ...
        return true
    }
}

from router-extras-module.