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
In my use case I have this domain-lang logic:
example.com: ['en', 'es']
example.mx: ['es']
and I have the following requirements:
for domains with 1 lang, do not show the lang in url, but for domains with 2 langs and more - show lang in url so it should be
example.com/es/user
example.mx/user
The problem
When I resolve locale as 'es' currently I am not able to build localised url properly because I don't know the current domain because the final url will depend on it. So I need to know the current domain from these functions getCanonicalPath and getLocalisedUrl
Any other proposals?
The text was updated successfully, but these errors were encountered:
I will focus next week on implementing a generalizable strategy across Paraglide JS 2.0 and all it's adapters, including NextJS. While I might not implement your desired strategy right away, I will keep your requirement in mind when I design the strategy API.
In my use case I have this domain-lang logic:
example.com: ['en', 'es']
example.mx: ['es']
and I have the following requirements:
for domains with 1 lang, do not show the lang in url, but for domains with 2 langs and more - show lang in url so it should be
example.com/es/user
example.mx/user
The problem
When I resolve locale as 'es' currently I am not able to build localised url properly because I don't know the current domain because the final url will depend on it. So I need to know the current domain from these functions getCanonicalPath and getLocalisedUrl
Any other proposals?
The text was updated successfully, but these errors were encountered: