Drop support for old rubocops #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viralpraxis
force-pushed
the
drop-support-for-old-rubocops
branch
from
e0b96b5
to
27d33ab
Compare
viralpraxis
force-pushed
the
drop-support-for-old-rubocops
branch
from
0f37d0c
to
5e6748d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A brief outline of the version requirements for the 4 most popular RuboCop extensions:
rubocop-performance: 1.48 (ref)rubocop-rails: 1.52 (ref)rubocop-rspec: 1.62 (ref)rubocop-minitest: 1.61 (ref)Old RuboCop versions fail on ruby-head and give me some headache, e.g. in #52 I can't use
RuboCop::Cop::AllowedIdentifiersbecause it was not implemented on rubocop's side few years ago.I bet almost no one uses rubocop < 1.48 (which was released over a year ago) because it's a very easy-to-upgrade gem