-
-
Notifications
You must be signed in to change notification settings - Fork 129
Issues: i18next/i18next-scanner
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Are there any plans to support TypeScript?
#237
opened Nov 16, 2022 by
KonradLinkowski
updated Sep 13, 2024
Why not merge this repo with i18next-parser?
#216
opened Sep 27, 2021 by
Elindorath
updated Sep 13, 2024
Return non-zero exit code on failure to extract strings
#256
opened Nov 28, 2023 by
djbb7
updated Nov 28, 2023
Trans component does not respect the defaultValue
#104
opened Oct 4, 2018 by
mariakatsourani
updated Jun 13, 2023
Reading
context
dynamically per tFunction
, TransComponent
#243
opened Jan 26, 2023 by
jlee0425
updated Jan 26, 2023
Following the steps at README.md does not produce the documented result. Something is wrong, perhaps me or perhaps the program.
#235
opened Aug 22, 2022 by
vituchon
updated Aug 22, 2022
why cant extract strings for packages from XRENGINE?
#232
opened Jun 6, 2022 by
johnfelipe
updated Jun 20, 2022
nodeToString
result doesn't match with react-i18n
#125
opened Jan 14, 2019 by
techird
updated Apr 23, 2022
The function passed to parseTransFromString is called multiple times.
#226
opened Mar 17, 2022 by
gomo
updated Mar 17, 2022
allow configuration of multiple set of dynamic context
#222
opened Oct 20, 2021 by
ForgottenR
updated Oct 20, 2021
Fallback key for <Trans> does not match react-i18next fall back key when using interpolation.
#187
opened Jun 19, 2020 by
kholland950
updated Jul 21, 2021
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-09-15.