Open Gui-FernandesBR opened 2 weeks ago
We should add a fallback linter: another linter that is run after pylint to capture eventual errors not captured by the main linter.
I would say that ruff
, the "yougest and fastest" player in the market right now, is our best candidate. I will let it for the next PR.
Flake8 would be the more "natural" option.
Maybe we could run flake8 AND also ruff.
@phmbressan I have fixed your comments. Please take in mind that I didnt't care too much about the errors threshold at this first time. I was more worried about getting everything to run.
Attention: Patch coverage is 71.18644%
with 119 lines
in your changes missing coverage. Please review.
Project coverage is 71.99%. Comparing base (
5c8e11a
) to head (5ed072c
). Report is 1 commits behind head on develop.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
We are going to officially adopt pylint in this repo.
Github Actions workflows erre updated:
I fixed
many
pylint errors, but it was a really hard task, quite time consuming. Therefore, I had to use pylint-silent to ignore some errors, those will be solved in the future, one by one.You don't have to read all the files. Focus on the new github workflow files and the .pylintrc file