-
Notifications
You must be signed in to change notification settings - Fork 0
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
Danger-warnings not working for pylint json report #29
Comments
Hi @grzegorzprzybyla-silvair As in Parsers documented, I only support the PyLint format So the easiest and fastest fix is to use If you use Jenkins to test your code, may I introduce you to danger-warnings_next_generation - an easy to use all in one solution. |
@grzegorzprzybyla-silvair |
I will check this :) |
Ok, even If I have change the output for my pylint:
pylint output:
danger local is still not returning any issues
|
Hi,
I would like to introduce danger-warnings into my python project.
But it seems like there is something wrong with pyLint json parser.
I've setup demo env to reproduce this issue:
Env:
demo project can be found here:
https://github.com/grzegorzprzybyla-silvair/python_demo
After executing bundle exec danger local, you can see following output:
Info:
+------------------+--------------------------------------------------------------------+
| Danger v6.0.9 |
| DSL Attributes |
+------------------+--------------------------------------------------------------------+
| violation_report | |
I've check and for bandit generated json it's working.
PyLint report is committed into project, so there are warnings inside
The text was updated successfully, but these errors were encountered: