-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
RSpec/FilePath exception with Rubocop 0.36.0 #62
Comments
I came across the same issue. For now I've disabled the specific check when using the latest rubocop. |
Looks like #60 has a fix for this |
Thanks @DexterTheDragon, #60 fixed this |
Any news on this one? |
Would love to see a release with this fixed, I've sadly had to uninstall this gem because it's holding back lots of other gems that require |
I just disabled the rule for now with: RSpec/FilePath:
Enabled: false |
Just tested the master branch with RuboCop |
This issue was fixed in the latest release 1.4.0. |
There are some incompatibilites between the latest version of RuboCop and rubocop-rspec which were fixed in this release. See: rubocop/rubocop-rspec#62
I've just been working through upgrading Rubocop to 0.36.0 and the RSpec/FilePath cop seems to be raising an exception for every file it checks. My rubocop-rspec is version 1.3.1, I believe this is up to date. Info string output by Rubocop at end of debug run:
The new
TargetRubyVersion
config has been set to2.2
(and the app currently runs 2.2.0, as you can see above) and we have no custom configuration for this cop.This is the full backtrace as given when I run Rubocop with
--debug
(mildly anonymised)The text was updated successfully, but these errors were encountered: