alternateLanguages URLs are not created using the routeResolver

[cerrutti (Sergio Cerrutti)]

Describe your question/issue in detail

The new routeResolver is awesome to resolve Prismic links in a Nuxt 3 application the easy way, but alternateLanguages comes without a resolved URL, and there is no way (as far as I know) to resolve them without a linkResolver. Is there any way to do this without cloning the resolver?

Something like that was discussed a few years ago for next.js:

Get resolved "url" in alternate_languages

Hello, I currently have a blog setup with this custom route: path: "/:lang/magazin/:category/:uid" (a fetch with 2 levels deep) and so I am currently fetching all my documents with get Static Paths in such a format: [category]/[uid] that corresponds to what my Router above is resolving. I am working with multiple languages, and so for each document (:uid) I also need the associated translated category (:category), for the language switcher, unfortunately the only answer I get from the al…

Impacted feature

alternateLanguages URLs.

[Pau]

Hey @cerrutti. There isn't another workaround for the case of resolving alternate languages URLs using the routeResolver. The answer in the linked thread remains the relevant solution at the moment.

We appreciate your understanding and patience as we work towards improving this functionality.

Thanks.