Move the department associated with Capybara::RSpecMatchers
to Capybara/RSpec/*
#113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR move the department associated with
Capybara::RSpecMatchers
toCapybara/RSpec/*
.Capybara/CurrentPathExpectation
,Capybara/SpecificMatcher
,Capybara/NegationMatcher
, andCapybara/VisibilityMatcher
cops depend on methods from theCapybara::RSpecMatchers
class.https://www.rubydoc.info/gems/capybara/Capybara/RSpecMatchers
This is breaking changes and will be planned during the major upgrade to RuboCop Capybara3.0.
Before submitting the PR make sure the following are checked:
main
(if not - rebase it).CHANGELOG.md
if the new code introduces user-observable changes.bundle exec rake
) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).If you have created a new cop:
config/default.yml
.Enabled: pending
inconfig/default.yml
.VersionAdded: "<<next>>"
indefault/config.yml
.If you have modified an existing cop's configuration options:
VersionChanged: "<<next>>"
inconfig/default.yml
.