Default Locale Redirection not Working about next-international HOT 8 CLOSED

in addition to having support for detect language maybe?
and thank you for the awesome lib, so far everything else has been working flawlessly in server components + client components,
without having to drill props nor complicated setup

from next-international.

Thanks for the kind words! I'll take a look at this issue.

from next-international.

The default locale serves as a fallback if no locale matches the Accept-Language header. Your browser might be configured to use English as the default locale, so next-international tries as much as possible to use the user's locale.

from next-international.

Wouldn't make more since if we can pass an argument ( which I thought the second param in the middleware is for ) to force default language? if its none existing we can use accept-language in this case

from next-international.

I don't think it's a good idea to force a specific language if users specifically set their preferred language. This goes against what the user expects.

I'm curious about what the community thinks about this. Feel free to add reactions if you agree/disagree to see what we should do in the future.

from next-international.

Well this is exactly why its only for default because some systems may focus on having a specific default language.

in case the user preferred language isn't supported how would it behave though? would it choose the default passed as default locale?

from next-international.

in case the user preferred language isn't supported how would it behave though? would it choose the default passed as default locale?

Yes, if the preferred language isn't configured in your app, it will use configured one (2nd argument)

from next-international.

Perfect
Thank you ao much🙏🙏🙏

from next-international.