-
Notifications
You must be signed in to change notification settings - Fork 906
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
Upgrade rubocop + rubocop plugins #1515
Conversation
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 looks solid to me. I largely agree with @fatkodima 's comments about some of the cops that might be better to disable rather than to autocorrect and enforce.
i'll make one more pass and try to revert the rules mentioned above. if it's not straightforward i'll have to abandon this attempt - i have very little time today to work on this and i don't want bike shedding to block the real reason i did this (#1514). |
…er_spec_type_from_file_location! to rspec
ok, i've addressed + fixed all the previous issues. if i don't hear anything else back in the next day i'll go ahead and merge. |
this pr upgrades
rubocop
to the most recent version. it also upgrades the various plugins we use to the most recent compatible versions. this unblocks #1513 (which requires a newer version ofrubocop
to support ruby 3.4).this pr includes all of the safe fixes (via
rubocop -a
) exceptGemspec/RequireMFA
(i'm not sure who has access to this onrubygems
so i didn't want to lock anyone out).all other errors were added to
.rubocop_todo.yml
viarubocop --auto-gen-config
.master
(if not - rebase it).code introduces user-observable changes.
and description in grammatically correct, complete sentences.