RSpec/RepeatedSubjectCall: do not report if subject is an argument to…

… a function call

CHANGELOG.md

@@ -3,6 +3,7 @@
 ## Master (Unreleased)
 
 - Fix beginless and endless range bug for RepeatedIncludeExample cop. ([@hasghari])
+- Fix a false positive for `RSpec/RepeatedSubjectCall` when subject is used as argument to function call. ([@K-S-A])
 
 ## 2.29.1 (2024-04-05)
 
@@ -978,3 +979,4 @@ Compatibility release so users can upgrade RuboCop to 0.51.0. No new features.
 [@ypresto]: https://github.com/ypresto
 [@zdennis]: https://github.com/zdennis
 [@zverok]: https://github.com/zverok
+[@K-S-A]: https://github.com/K-S-A

lib/rubocop/cop/rspec/repeated_subject_call.rb

@@ -72,6 +72,7 @@ def on_top_level_group(node)
 
         def detect_offense(subject_node)
           return if subject_node.chained?
+          return if subject_node.parent.send_type?
           return unless (block_node = expect_block(subject_node))
 
           add_offense(block_node)

spec/rubocop/cop/rspec/repeated_subject_call_spec.rb

@@ -114,6 +114,17 @@
     RUBY
   end
 
+  it 'does not register an offense when `subject` as an argument' do
+    expect_no_offenses(<<~RUBY)
+      RSpec.describe Foo do
+        it do
+          expect { create(:bar, baz: subject) }.to change { A.count }
+          expect { create(:bar, subject) }.to not_change { A.count }
+        end
+      end
+    RUBY
+  end
+
   it 'does not register an offense when `subject` with not expectation' do
     expect_no_offenses(<<~RUBY)
       RSpec.describe Foo do