You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, currently there is no tooling to ensure consistency:
identify unused strings (strings present in JSON files but not used - anymore - in JS or Python codebase)
identify missing strings (strings present in JS or Python codebase but not present in JSON files - must be present in at least en for proper operation and in qqq for proper TranslateWiki operation)
The text was updated successfully, but these errors were encountered:
I think we first need to check if such a tool does not already exist. Be aware that while all translated strings are stored in JSON files, they are used both in .vue and Jinja2 templates. They could theoretically soon be used in .py files.
If it does not exist, then I would suggest to develop a small Python script doing the job. Be aware that we need both directions, i.e. flag any keys present in the JSON but not used in the code AND flag any keys used in the code but not present in at least en and qqq JSON files.
This Python script should exit with non-zero exit code when problem(s) are detected, and we can add this script to invoke tasks.py and the the QA CI.
I will soon merge #69, so this will be easier to work on.
With #69, we have introduced i18n.
However, currently there is no tooling to ensure consistency:
en
for proper operation and inqqq
for proper TranslateWiki operation)The text was updated successfully, but these errors were encountered: