Version 0.11.0 aka The New Violation Codes
We had a really big problem: all violations inside best_practices
was messed up together with no clear structure.
We had to fix it before it is too late.
So, we broke existing error codes.
And now we can promise not to do it ever again.
We also have this nice migration guide
for you to rename your violations with a script.
Features
- Breaking: replaces
Zerror code toWPScode - Breaking: creates new violation group
refactoring.py - Breaking: creates new violation group
oop.py - Breaking: moving a lot of violations
frombest_practicestorefactoring,oop, andconsistency - Adds new
wemakeformatter (using it now by default)
Bugfixes
- Fixes error message of
OverusedStringViolationfor empty strings - Now does not count string annotations as strings for
OverusedStringViolation - Fixes
InconsistentReturnVariableViolationwas raised twice
Misc
- Adds migration guide to
0.11 - Improves legacy guide
- Adds
--show-sourceto the default recommended configuration - Adds better docs about auto-formatters
- Adds
autopep8to CI to make sure thatwpsis compatible with it - Ensures that
--diffmode works forflake8 - Renames
IncorrecttoWrongwhere possible - Renames
IncorrectlyNestedTernaryViolationtoNestedTernaryViolation - Renames
IncorectLoopIterTypeViolationtoWrongLoopIterTypeViolation