-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
"Warning: unrecognized cop RSpec/DescribeClass" on running rubocop
#32
Comments
@geniou Any idea what's up here? |
@dleve123 sorry for the delay. I tied to reproduce the problem but I had no success. It is strange because when the |
@geniou Thanks for helping out! We are not running |
Just figured out a semi-solution - for anyone looking at this in the future or if you think this is actually a bug and should be fixed or if this tells us the problem with our setup... Adding |
@GolfyMcG thanks that worked for me |
Is this still an issue for anybody? |
@nijikon we have not changed our |
No problems here anymore. Rubocop 0.37.2, rubocop-rspec 1.4.0. |
However, when running with
|
I'm running Rails 4.2.1 and Rubocop 0.37.2 and getting a ton of require: rubocop-rspec
AllCops:
Exclude:
- 'bin/**/*'
- 'config/**/*'
- 'db/**/*'
- 'spec/spec_helper.rb'
- 'spec/rails_helper.rb'
- 'Rakefile'
Documentation:
Enabled: false
Metrics/LineLength:
Max: 200
Metrics/ClassLength:
Max: 500
Metrics/ModuleLength:
Exclude:
- 'spec/**/*_spec.rb'
Rails:
Enabled: true
RSpec/DescribeClass:
Exclude:
- spec/requests/**/*
- spec/routes/**/*
- spec/support/**/*
Style/TrivialAccessors:
Exclude:
- spec/**/* |
@kWhittington it should be |
@andyw8 that was just a typo in the comment, I've updated my sample Rails:
Enabled: true inside of |
@nijikon we're still seeing warning
With following entry in rubocop.yml:
rubocop-rspec (1.4.0) |
@kowal: Try |
@andyw8 yup that was a typo :) thx! |
Is anyone still experiencing this issue? It seems like the |
It works using |
@aried3r thats currently out of rubocop-rspec's control. See rubocop/rubocop#3414 |
Some debugging info:
$ cat Gemfile.lock | grep rubocop rubocop (0.29.0) rubocop-rspec (1.2.1) rubocop rubocop-rspec
Looks like the
rubocop-rspec
cops are successfully being ignored (commenting out the disabling of them causes cop failures), so the warning is very odd.RSpec/DescribeClass
is failing because it is the firstrubocop-rspec
being encountered. In other words, if I reordered the declarations ofrubocop-rspec
's cops in the TODO file, the very firstrubocop-rspec
cop will appear in the warning.Please let me know if more information is needed!
The text was updated successfully, but these errors were encountered: