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
Non-zero exit code on found problems #20
Comments
Understood, will try to work on this over the weekend.
Feel free to open an issue about this as well. I'd be happy to update the rule if you feel it is noisy. |
Any news on this? We also would like to integrate statix into our CI but without proper return codes its useless to us. |
Sorry, this slipped my radar again, the next release will contain this fix. |
How about adding a -q argument like grep? |
i have opened #34 to fix this, behavior is as follows:
|
@SuperSandro2000 hmm, is that any different from redirecting all output of statix to |
One thing that I think grep does along with just silencing output is to exit immediately as soon a single match is found and not doing the full search. |
I checked statix today and except for the unquoted splices (#8) and empty pattern I agree with its suggestions on my projects and I'd like to add it to CI.
Though to make any use of it in CI, it is required that we get a non-zero exit code on found suggestions.
The text was updated successfully, but these errors were encountered: