-
Notifications
You must be signed in to change notification settings - Fork 52
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
Audit functionality #33
Comments
I'm wondering what the best way would be to get these warnings (and other errors) in a machine-readable manner. Use case: we currently programmatically extract strings from our projects after each push to GitHub and import them into GlotPress. On success, we send a notification to our Slack channel. Now I want to do the same for errors as well. Do I need to parse the terminal output using regex, or hold the messages in Many commands have a @schlessera Would love to hear your insights on this :-) |
I've already helped build a similar thing here: https://github.com/fklein-lu/checker-cli/tree/master/src Basically, it is a generalized pipeline running one or more The With this object model, you can easily write multiple |
Very helpful, thanks! Will try to explore this concept a bit for the make-pot command so we could eventually add a In the mean time I guess we'll resort to parsing the output on our own in our script. |
Just thinking out loud after reading through https://core.trac.wordpress.org/ticket/44139.
We might be able to generate some warnings when a string occurs multiple times in the source code but with multiple translator comments. That‘s usually an indication that these should be separate strings with different contexts.
The text was updated successfully, but these errors were encountered: