-
Notifications
You must be signed in to change notification settings - Fork 37
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
Embrace parseable output to stdout #74
Comments
FWIW here's my playground: https://github.com/webknjaz/ansible-gentoo-laptop/pull/4/checks?check_run_id=35656446 |
If there is a PR that would fix this, let me know. I've had a rereview of #28 but that needs a rebase and I'm still not convinced by the custom option parser. |
Yeah, I'm also not sure whether that solution is a good fit. The problem is that I don't know whether it needs architectural changes to unify output format as well. |
It is common to print smth parseable for the sake of pipe chaining among POSIX utils.
However, ansible-review doesn't seem to care about this:
I'm building a GitHub App integration demo, which would really benefit from not having to use heuristics and manual conditional parsing to retrieve structured result data.
The text was updated successfully, but these errors were encountered: