-
Notifications
You must be signed in to change notification settings - Fork 96
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.
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
Refactor with/against Rubocop #405
Conversation
For reference, here's a list of all style errors found in 731.1, with an example for each one:
|
Some comments on the rules I don't totally agree with:
Thanks for starting this ! |
No problem! I agree with you on most things. Also, what happens if Rubocop changes policy later on, is sup then refactored again? When I opened #402 I didn't expect there to be over 5k violations. Im wondering if it wouldn't be a better approach to disable all rules and then incrementely enable rules? |
😃 Sorry for not mentioning that this is very likely to happen. But ....
This is possible. I suggest to fix those violations incremental by:
Cheers, |
|
BTW: Nice to see |
I think ill stop at this point, as the rest requires major refactoring of the source instead of minor edits. |
@rakoo wrote
In many cases I'd expect that extracting blocks as methods would clean the source in addition to getting rind of the style violations. That way you also get to give a name for the operation the piece of code does and thus ad semantics. |
In response to #402. I've implemented Rubocop for this project.
Created this PR in case someone wants to help out?