Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18next - namespaces not picked up, <Trans> not pickedup up #1211

Open
VinzentE opened this issue Sep 24, 2024 · 0 comments
Open

i18next - namespaces not picked up, <Trans> not pickedup up #1211

VinzentE opened this issue Sep 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@VinzentE
Copy link

VinzentE commented Sep 24, 2024

Some variants are not beeing picked up by ally.

Example 1:
const title = t('someNamespace:title')

The notation {namespace}:{key} is not detected.

Example 2:
This variant is being picked up
field.time.description

But this variant is not
<Trans i18nKey={'field.time.description'} />

Any ideas? Is that due to wrong settings or missing support or a but?

@VinzentE VinzentE added the bug Something isn't working label Sep 24, 2024
@VinzentE VinzentE changed the title i18next - namespaces not picked up, YTransy not pick i18next - namespaces not picked up, <Trans> not pickedup up Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant