-
Notifications
You must be signed in to change notification settings - Fork 44
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
Adding rubocop-capybara
as a required extension in configuration breaks build
#346
Comments
Just an aside question: are there any environment variables present during the build process which can be used to determine the environment is CodeClimate? A cursory Google search didn't yield anything. For the time being, in order to not roadblock my end, I was thinking to conditionally exclude |
Having The reason for the inclusion of the department is that starting with Rubocop Rspec major version 3 many of the departments (Cabybara, FactoryBot, etc) have been extracted out of the dependency. See the release: https://github.com/rubocop/rubocop-rspec/releases/tag/v3.0.0 And the specific changes which extracted out Rubocop Rspec Rails: rubocop/rubocop-rspec#1830
|
Adding
rubocop-capybara
to the "required extensions" list in.rubocop.yml
configuration file breaks the build on CodeClimate.A snippet of the require list in the
.rubocop.yml
:A screenshot of the build error:
Our CodeClimate setup is using the
beta
channel. Running rubocop locally executes without issue.The expectation is for the CodeClimate to run successfully.
The output log of the CodeClimate error:
The text was updated successfully, but these errors were encountered: