Can't switch to specific locale *by path* if route path was customized

[mattickx]

Version

v6.7.0

Reproduction link

#554

Steps to reproduce

Please add following tests:

expect(window.$nuxt.localePath('/about-us', 'fr')).toBe('/fr/a-propos')
expect(window.$nuxt.localePath({ path: '/about-us' }, 'fr')).toBe('/fr/a-propos')

Which will fail as both will result in /fr/about-us instead of /fr/a-propos
Tested with master branch.

What is expected ?

localePath('/about-us', 'fr') to be /fr/a-propos

What is actually happening?

localePath('/about-us', 'fr') becomes /fr/about-us

Additional comments?

Using the older way with route names still works correctly, but this usage would make my life easier.

_{This bug report is available on Nuxt community (#c426)}

[rchl]

It's not really about #554 as that one just matched what was already possible before (your second test). The thing is that is not really supposed to work. In theory, we could try to come up with some solution but that would be an extra feature that would require storing a map of paths assigned to a specific route.

[rchl]

Those finding this issue should know that it works when passing route's "name" to localePath rather than a path.

Every page route has a name attached to it. They follow certain pattern but if unsure, one can always look inside generated .nuxt/router.js file, at the list of routes.

[FreekVR]

I'm having the same issue, even without supplying the second parameter with the alternative language it's not working sometimes for customized paths.

(An alternative to using the .nuxt/routes.js source-file is to use the "Router" tab in your browser's Vue Devtools)

[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.

[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.

[katerlouis]

It's also not working for me.
Shouldn't the docs be updated then?

Or is there a way to fix this / support this functionality?

[rchl]

It's also not working for me.
Shouldn't the docs be updated then?

The docs could always be improved to make things clearer.
That said, that example is not necessarily wrong as that works for cases when route names are not customized.

Or is there a way to fix this / support this functionality?

There is. That's why this feature request is open. :)

[katerlouis]

Is the following what you mean by "customized"?

nuxtI18n: {
  paths: {
    de: '/karriere',
  },
},

[rchl]

Yes. This or through the pages module configuration option.

[katerlouis]

Okay, I just checked it, and yeah you're right. So basically localePath('/career') only prepends the locale and doesn't take customized paths into consideration.

Please correct me if I'm wrong, but it feels like supporting customized paths for this path-parameters shouldn't be too difficult, right?

[rchl]

It's fairly complex to implement that in a robust way.

To add to that, there is currently no support for custom paths when using NO_PREFIX strategy but there should be. That needs to be taken into consideration when implementing this feature.

There is some veeeery early attempt at that in https://github.com/nuxt-community/i18n-module/tree/fix/no-prefix-rename

[Energon7]

@rchl fix here: #1088

[rchl]

Please hold off announcing a fix before it's properly tested and reviewed.

[rchl]

Should be fixed by #1088