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
Disable pending cops when running rubocop #9136
Conversation
I am on the fence regarding this. I refrained from enabling certain cops (ones concerned with patterns and numbered parameters) in the aforementioned pull request because they were related to Ruby 3 syntax which Jekyll has not yet adopted. |
Aha I see. Is there a problem enabling them even if Jekyll's syntax is still following ruby 2.x? They will not be triggered until someone tries the new syntax, right?
Do you mean noisy as entries in rubocop.yml, the cop recommendations themselves? I am not very opinionated when it comes to which cops should be enabled or not (especially since I'm new to the codebase). The main point of this PR is to have a warning-free |
Personally, I feel enabling unnecessary cops means redundancy.
I like this alternative. Especially since that is your primary goal with this PR. |
I buy the argument 👍
Done :) |
Thanks @yboulkaid |
Youssef Boulkaid: Disable pending cops when running rubocop (#9136) Merge pull request 9136
Summary
In #9125 we bumped the rubocop version to 1.36, which introduces new
cops. Unconfigured cops output a warning when running
script/fmt
,which was noisy.
This PR makes rubocop run with the
--disable-pending-cops
optionto make the script output cleaner.