-
Notifications
You must be signed in to change notification settings - Fork 285
RuboCop 0.72.0 removed -R option, causing Rails linting to fail #598
Comments
Is there a config file based workaround for this in the meantime? I've tried downgrading to 0.71 but it throws a few requirement errors for some other gems. |
Actually, got it working with a mix of older gem versions:
But obviously, support for the latest versions would be preferred. I'm new to VSCode, so I'll have a poke around how extensions work and see if I can muddle a PR together at some point. |
@jordanbrock Here's what I did to get linting working with rubocop >0.71
|
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
I can make a PR to update the docs later this week with the suggestion from @abraham-chan |
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
This still an actual problem. Experienced it today. Using |
still a problem |
Still seeing this issue more than a year later, currently using #598 (comment) as a workaround! |
Your environment
vscode-ruby
version:0.27.0
any
asdf
1.43.2
macOS 10.14.6
useLanguageServer
is true in your configuration?)Yes
>0.72.0
Expected behavior
Adding this to my configuration should enable linting with rubocop, with rails cops enabled.
Actual behavior
Language Server Output:
RuboCop Changelog
The new way to use rails cops is to install the
rubocop-rails
gem and run RuboCop withrubocop --require rubocop-rails
I can make a PR for this to swap out the argument, but to maintain compatibility with older rubocops it may become more complicated.
The text was updated successfully, but these errors were encountered: