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
Update the Rubocop config #107
Conversation
to make it work with Rubocop 0.40.0
# Do not check the module length, the YCP converted includes | ||
# are usually too long. | ||
Metrics/ModuleLength: | ||
Enabled: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is wrong, we do not do it even for class length or method lenght...It is intentionally undefined, so if you generate rubocop config it adds current value and it try to check that it is not increased.
now it in general looks good, but I think that it deserve some discussion on mailing list about backward compatible ones, so we can decide which way we prefer and maybe we can force now recommended value? In general I think we should follow upstream guide unless we have good reason to change it. And backward compatibility in style guide is not good reason for me as it can be auto-corrected. |
OK, makes sense, initially I wanted to change the code as little as possible, but the argument about the upstream compatibility is really strong. I'll update it... |
# Allow block.call: | ||
# | ||
# def foo(&block) | ||
# var = block,call |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dot instead of comma
LGTM |
LGTM |
to make it work with Rubocop 0.40.0