Is there any way to have a different dynamic route before [locale]?

[gajda-w]

I'm building an application where the requirement is for the link to look like the following: domain.com/[region]/[language]. However, when I add another dynamic route above the [locale] route in my current implementation, the language is taken from the highest dynamic route, which is [region]. This is quite a non-standard configuration; I know that standardly it might be something like en-US, but is there any option to achieve it the way I described?

Can I somehow instruct next-intl to use the values in the [locale] route rather than the one above it?

[amannn]

You're probably looking for this: #653

[gajda-w]

Looks great, thank you! 🙏