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
Hound fails to merge RuboCop configuration properly #1842
Comments
This is because Hound simply merges organization-wide configuration into project-specific one, instead of relying on RuboCop's inheritance rules: hound/app/models/config/rubocop.rb Line 12 in fe43c07
|
To clarify: It isn't a problem when overriding specific cop, but it is a problem when overriding the whole department. Due to incorrect merging, more specific |
Hound inherits organization-wide Ruby style book in a different way than RuboCop.
Given organization-wide .rubocop.yml
and project-specific .rubocop.yml:
Hound reports violations of
Metrics/MethodLength
, whereas local RuboCop does not (cop is disabled as expected). IMO Hound's behaviour is incorrect.RuboCop 1.5.2 in both cases.
The text was updated successfully, but these errors were encountered: