quality
quality copied to clipboard
Published
20 hours ago •
apiology
apiology
Reek
Reek doesn't seem to behave nicely under the rules here--the level of effort to address warnings (at least for me) and the number of hard-to-address/undesirable warnings (at least in my maybe limited understanding of effective refactoring) doesn't seem to be compatible with ratcheting.
I find myself often disabling reek--wonder if it it should be in by default or should use a different ratcheting algorithm or something like that.
Maybe make the calculation to be ratcheted be the average number of violations per line of code?