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

Tools: add a tool to check that no translations are missing #389

Open
warpdesign opened this issue Feb 19, 2023 · 1 comment
Open

Tools: add a tool to check that no translations are missing #389

warpdesign opened this issue Feb 19, 2023 · 1 comment

Comments

@warpdesign
Copy link
Owner

warpdesign commented Feb 19, 2023

With already 3 translations, it will be easy to miss/forget to translate a string. There should be a tool that's run on precommit/prepush that checks that all strings from en.js are translated.

There could be something useful here: https://www.i18next.com/overview/plugins-and-utils

@prajwalhaniya
Copy link
Contributor

prajwalhaniya commented Feb 27, 2023

I tried implementing this in my local development, I am able to parse the JSON files through i18next-parser. But, I am not able to generate the output to a specific folder, so that I can compare them and give an output of missing strings. Am I doing it right? I am stuck a little at this point.
I have created a folder called public and locales for test purposes.

2
1

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