Fix an error for Capybara/RSpec/HaveSelector
when passing no arguments
#129
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.
ruby-lsp
constanty runs RuboCop over code while typing, so this error will just happen.Do note that there are currently 2 RuboCop offenses introduced through new
rubocop
versions:The second one seems pretty straightforward, the other I'm not sure about. It seems fine to me but when the cop is ran the fetched config is just empty. I'm not sure why but a commit similar to this would fix it: rubocop/rubocop-rails@5180fa2 (i.e. adding
rubocop-capybara
to its own.rubocop.yml
file.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).