-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix bad merge for Style/OptionHash #2105
Conversation
4ea259a
to
3f75d76
Compare
This line was introduced in a5be58e, but accidentally deleted when merging 35ef5ed. I put this in my .rubocop.yml file. ```` Style/OptionHash: Enabled: true ```` And got the following error: ```` Warning: unrecognized parameter Style/OptionHash:Enabled found in .rubocop.yml ```` It looks like we need to specify `Enabled: false` by default for it not to complain.
Oo good catch! |
Fix bad merge for Style/OptionHash
👍 Thanks! |
@wli is it correct that I should still be getting this error even if I put: Style/OptionHash:
Enabled: true In my |
@jfelchner Which version of rubocop are you running? This fix is only in master, and hasn't been released yet. |
@wli latest but I figured since all it was, was adding that to the YAML file, I could just add it to my YAML file and fix it myself. |
@jfelchner Unfortunately it seems like rubocop complains if the Not sure really how the internals play out and if there's any way to fix it yourself locally, but luckily it's just a warning and won't block. Maybe @bbatsov can shine some light on this? |
👍 |
@wli The warning for unrecognized parameter is issued when local configuration contains a parameter that's not found in default configuration, i.e., |
This line was introduced in a5be58e, but accidentally deleted when merging 35ef5ed.
I put this in my .rubocop.yml file.
And got the following error:
It looks like we need to specify
Enabled: false
by default for it not to complain.