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
Is your feature request related to a problem? Please describe.
The issue is how to reuse translations efficiently. Currently only a single namespace can be used by useTranslations, which means we cannot have shared namespaces.
Thank you for the report, I definitely understand your request!
This has been discussed a few times before, the latest being #217.
There are currently no plans to support this because:
It would make the TypeScript integration significantly more difficult (if possible at all)
It increases the API surface for something that can already be achieved today (useTranslations()—i.e. no namespace), possibly getting in the way of a potential feature in the future
It introduces ambiguity which message to resolve to when there's overlap (e.g. ns1.title and ns2.title)
The structuring messages section in the docs has more information on this topic.
As mentioned, I understand the request, but I think this API is for the time being not a good direction for next-intl, especially since there are escape hatches.
Is your feature request related to a problem? Please describe.
The issue is how to reuse translations efficiently. Currently only a single namespace can be used by
useTranslations
, which means we cannot have shared namespaces.Describe the solution you'd like
Describe alternatives you've considered
All alternative libraries support this. The issue they have is bad integration with next. But this feature is really really important.
The text was updated successfully, but these errors were encountered: