-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Update .rubocop.yml, and disable OnSendWithoutOnCSend #2026
Conversation
c758730
to
81f492d
Compare
My internal parser broke on |
I haven't looked through all the cops in here but it might be that the |
We keep InternalAffairs/OnSendWithoutOnCSend disabled, with the following reasoning (almost verbatim quoted from @dvandersluis[^1]): > Maybe the OnSendWithoutOnCSend cop doesn't make sense for > rubocop-rspec. There are not a lot of instances where safe navigation > would be used in tests, and anywhere that we're calling a method on a > constant or as a macro doesn't really need safe navigation support. [^1]: #2026 (comment)
81f492d
to
9eb77cd
Compare
I decided to follow @dvandersluis’ advice and outright disable the OnSendWithoutOnCSend cop. I have update the PR to also include enabling of all pending cops up until the latest version. |
f8f762a
to
9eb77cd
Compare
The oldest version of RuboCop may not be able to read our configuration file. That doesn't matter, we just need the version number, and assurance that the specs can run.
We keep InternalAffairs/OnSendWithoutOnCSend disabled, with the following reasoning (almost verbatim quoted from @dvandersluis[^1]): > Maybe the OnSendWithoutOnCSend cop doesn't make sense for > rubocop-rspec. There are not a lot of instances where safe navigation > would be used in tests, and anywhere that we're calling a method on a > constant or as a macro doesn't really need safe navigation support. [^1]: #2026 (comment)
9eb77cd
to
3210f7d
Compare
A new cop InternalAffairs/OnSendWithoutOnCSend was added to RuboCop in rubocop/rubocop#13719.
cc @dvandersluis