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

Static extraction of i18n strings #588

Open
jeanregisser opened this issue Sep 27, 2024 · 1 comment
Open

Static extraction of i18n strings #588

jeanregisser opened this issue Sep 27, 2024 · 1 comment

Comments

@jeanregisser
Copy link
Contributor

jeanregisser commented Sep 27, 2024

In order to improve the developer experience for hooks author, we'd like to statically extract i18n strings from the code base.

There are several tools which can do this with i18next:

static extraction tools can read through your code files to automatically find and export translation keys. i18next-scanner, i18next-parser and babel-plugin-i18next-extract are sensible choices to achieve this goal.

https://www.i18next.com/how-to/extracting-translations

It would be nice to have a GitHub workflow check that ensure the latest strings have been extracted.
The workflow could also directly run the extraction if the PR author forgot to do it.

@Valortin
Copy link

Valortin commented Feb 4, 2025

@jeanregisser Please I would love to get assigned to this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants