Update RuboCop config for 1.8 compatibility #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RuboCop has recently released version 1.8, which triggers new warnings with our current configuration:
Naming/PredicateName
cop has been renamed toNaming/PredicatePrefix
.rubocop-rails
,rubocop-performance
, andrubocop-rspec
extensions now support plugins. You should specifyplugins: ...
instead ofrequire: ...
in your configuration files.See: https://docs.rubocop.org/rubocop/plugin_migration_guide.html
To address these, I have created a
rubocop-1.8
branch containing the necessary adjustments.This pull request will not be merged immediately; we will wait until our main applications have upgraded to RuboCop 1.8.
If you want to use RuboCop 1.8 in your project before then, update the
inherit_from
attribute in your.rubocop.yml
to point to therubocop-1.8
branch: