Add a CLI command to validate the catalog on CI
See original GitHub issueIs your feature request related to a problem? Please describe.
One of the common problem with localization process is that as a developer you have to not forgot to run lingui extract
before committing new/edited/removed string.
Describe proposed solution
Add a CLI command like lingui check-catalog
that verify that all the key of the application are present in all catalog. It will return an errored exit code if some string are not referenced in the catalogs.
A verbose mode could also print the location of the missing messages.
I work on it if your ok with the idea
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:11 (4 by maintainers)
Top Results From Across the Web
How to use the CircleCI local CLI
You can validate your orb with the following: ... This CLI pack command (separate to circleci orb pack described above) allows you to...
Read more >ServiceNow CLI available commands
Skips validation of the given scope name. Default: false . Run the development server. Add your component code and test it using a...
Read more >Validate apps against company policies in a CI pipeline
Fix the app to comply with company policies · In Cloud Shell, add a commonLabels section to the base Kustomization file: cat <<EOF...
Read more >Unity Catalog CLI | Databricks on AWS
Learn how to use the Databricks Unity Catalog command-line interface. ... Validate an external location and credential pair.
Read more >Publishing Assets Using API Catalog CLI
You can use the api-catalog publish-asset command to publish your API definitions to Exchange. Embed this command in your automation tools, such as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi there, I’ve also observed the issue that @armandabric described, forgetting to run
lingui extract
and committing the changes seems to be quite common. As a result, changes in.po
files often end up in later commits or even later pull requests, in which case it tends to make the code review process slightly confusing.I found the following command quite useful to check that there are no uncommitted changes after running
lingui extract
:However, this can only work when it’s executed in a git repository, which is not always the case in a CI setting. Something like
lingui extract --check
or--dry-run
with appropriate exit codes would be very useful 👍I will propose you something in the next weeks