-
Notifications
You must be signed in to change notification settings - Fork 16
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
Consider removing rubocop-minitest dependency #13
Comments
Related to this issue, how does one require Here is what I have below: require:
- rubocop-rspec
inherit_gem:
rubocop-rails-omakase: rubocop.yml I can't get After removing the inherit gem I can get My guess is there is conflict with the https://github.com/rails/rubocop-rails-omakase/blob/main/rubocop.yml#L1-L4 Can anyone steer me in the right direction? |
@vietqhoang this is the config I use usually: inherit_gem:
rubocop-rails-omakase: rubocop.yml
rubocop-rspec: config/default.yml
rubocop-faker: config/default.yml
action_policy: config/rubocop-rspec.yml
test-prof:
- config/default.yml
- config/rubocop-rspec.yml
require:
- test_prof/rubocop
- rubocop-faker
- rubocop-rspec
- rubocop-md
|
Thanks for sharing your config. It led me to get my configuration working. inherit_gem:
rubocop-rails-omakase: rubocop.yml
rubocop-rspec: config/default.yml
require:
- rubocop-rspec One other question. Although the cops are working as expected, I am experiencing a lot of output noise from
Thanks again. And sorry for derailing the issue. |
I have the same warnings when |
Closes rails#13. This PR drops rubocop-minitest from gem dependency. In fact, the `Minitest` department's Cop is not used in rubocop-rails-omakase: https://github.com/rails/rubocop-rails-omakase/blob/v1.0.0/rubocop.yml This means that it might be appropriate for users to add the `Minitest` department's cop only when they start using it. As a result, there will be no need to install gems that are not included in the rubocop-rails-omakase configuration. Users can be given the choice to add cops based on the testing framework they are using.
I am not quite sure that having
rubocop-minitest
as a dependency is correct. On one side – yes, Minitest is a default testing framework in Rails; on the other side, a lot of Rails apps use RSpec, and havingrubocop-minitest
in the dependency graph will look quite strange.What do you think?
The text was updated successfully, but these errors were encountered: