Open kratob opened 1 week ago
Seems like this works with rubocop-rspec >3.0 again https://docs.rubocop.org/rubocop-rspec/3.0/upgrade_to_version_3.html
They have extracted Capybara
and FactoryBot
from rubocop-rspec but left Rspec/Capybara
and Rspec/FactoryBot
in version < 3.
In another customer project with it's own rubocop fork, I removed the listed cops from rspec.yml
within the gem because they are also in capybara.yml
or factory_bot.yml
.
@FLeinzi is rigtht, but we actually did already disable the nested cops like Rspec/Capybara, so I'm a bit confused, why you are even being notified about Cops that are disabled. But we will look into it, and as an upgrade to rubocop-rspec > 3 seems to fix it, that seems to be the most logical approach.
@FLeinzi is rigtht, but we actually did already disable the nested cops like Rspec/Capybara, so I'm a bit confused, why you are even being notified about Cops that are disabled. But we will look into it, and as an upgrade to rubocop-rspec > 3 seems to fix it, that seems to be the most logical approach.
As I said, I just removed them on this customer's fork from the file. I guess that rubocop complains about the definition.
In rubocop-rspec > 3 they removed the dependency on rubocop-capybara and rubocop_factory-bot but they also extracted another gem "rubocop-rspec_rails". I don't know whether I like this approach. In the end we have 1,000 rubocop gems. :sweat_smile:
After updating to the latest version of makandra-rubocop, I get a wall of warnings:
It seems to me I also get all the Capybara and FactoryBot matchers without ever having asked for them, probably simply because the cops are a dependency of makandra-rubocop now.