Two translations namespaces, plugin uses the wrong translation #1226
Labels
bug
Something isn't working
Comments
|
Can confirm, same issue. next-intl Initialisation: const t = useTranslations("auth.loginPage");
const t_validation = useTranslations("validation");
const t_common = useTranslations("common");
header should the: Only known workaround is: const t = useTranslations();
[...]
<h1 className="text-3xl font-bold">{t("auth.loginPage.header")}</h1>
<p className="text-balance text-muted-foreground">{t("auth.loginPage.headerDescription")}</p>
[...]
<FormItem>
<div className="flex items-center">
<FormLabel>{t("common.password")}</FormLabel>
[...] |
|
Facing the same issue |
|
With the current implementation, only the last instance of // Find matches of `useTranslations`, later occurences will override
// previous ones (this allows for multiple components with different
// namespaces in the same file).
const regex = /useTranslations\(\s*(['"`](.*?)['"`])?/g
... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
So in my React TSX file I have two "useTranslations":
When I go and use
tthe following code says:<h2>{ t('selection', { circuit: race.circuit }) }</h2>:en: i18n key "generic.selection" does not existWhen I use
tGenericit doesn't even recognize the translationExtension Version
i18n Ally: v2.12.0
Framework/i18n package you are using
Next.js (+ Typescript) & package:
next-intlTo Reproduce
Steps to reproduce the behavior:
useTranslationsDevice Infomation
Extension Log
Go to
View->Output->i18n Ally, and paste the content below. You should mask any sensitive informationScreenshots
The text was updated successfully, but these errors were encountered: