-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Cop idea: Replace equal
with be
#1676
Comments
Both matchers exist in RSpec. Are they always interchangeable? |
If any arguments pass, the matchers will be equal. https://github.com/rspec/rspec-expectations/blob/main/lib/rspec/matchers.rb#L349
In my opinion the |
Can you prove that by harvesting real-world-rspec? I’d specifically be interested in cases where the argument is not among nil/true/false. |
Related: #933. |
@pirj I've searched in
and
|
Reference: https://github.com/rspec/rspec-expectations#identity
Actual behavior
I have the following spec:
I run rubocop and don't get any offences:
Expected behavior
Rubocop
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop -V 1.54.1 (using Parser 3.2.2.3, rubocop-ast 1.29.0, running on ruby 2.7.8) [x86_64-linux] - rubocop-capybara 2.18.0 - rubocop-factory_bot 2.23.1 - rubocop-performance 1.18.0 - rubocop-rails 2.20.2 - rubocop-rake 0.6.0 - rubocop-rspec 2.22.0 - rubocop-thread_safety 0.5.1
The text was updated successfully, but these errors were encountered: