You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #530, we should use the new ruff linter to achieve significant speedups.
ruff is meant to replace all other linters in the current pre-commit and CI definitions.
ruff also should be used for formatting instead of black.
Linter rules are up for discussion while implementing.
The text was updated successfully, but these errors were encountered:
Having used it a bit in another project, I have to admit that I like ruff. It's fast and automatically resolves many of the issues instead of just complaining about them.
I think this issue is missing some details. Could you please answer these questions in the description?
Would ruff be added to the existing hooks or would it replace them?
Should we also use ruff's formatting instead of black's formatting? If so, we should be careful to ignore the specific commit that reformats the code in the git history.
What new linter options would be enabled? I would also err on the side of too little rather than too much.
As discussed in #530, we should use the new ruff linter to achieve significant speedups.
ruff is meant to replace all other linters in the current pre-commit and CI definitions.
ruff also should be used for formatting instead of black.
Linter rules are up for discussion while implementing.
The text was updated successfully, but these errors were encountered: