Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Reek #74

Open
apiology opened this issue Oct 8, 2016 · 1 comment
Open

Reek #74

apiology opened this issue Oct 8, 2016 · 1 comment

Comments

@apiology
Copy link
Owner

apiology commented Oct 8, 2016

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.
@apiology
Copy link
Owner Author

apiology commented Oct 8, 2016

Maybe make the calculation to be ratcheted be the average number of violations per line of code?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@apiology