You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using RSpec with autocorrect I assumed it wouldn't break my codebase
Actual behavior
In cucumber-ruby-core it replaced be_match with match. However these weren't correct, because the codebase had defined match? as a method. So the correct behaviour here is to detect that the method match? has been defined, and then not suggest an autocorrect or error here.
Expected behavior
When using RSpec with autocorrect I assumed it wouldn't break my codebase
Actual behavior
In
cucumber-ruby-core
it replacedbe_match
withmatch
. However these weren't correct, because the codebase had definedmatch?
as a method. So the correct behaviour here is to detect that the methodmatch?
has been defined, and then not suggest an autocorrect or error here.Steps to reproduce the problem
cucumber/cucumber-ruby-core@release/v13.0.3...main#diff-146e0d9fad5351a0fc7a77b7bb4e47a19b46a83e67e03c9330cd294077be02abL65)
RuboCop RSpec version
The text was updated successfully, but these errors were encountered: