Yudai Takada

> Is this an issue from the real code? Why would anyone want to use that? Yes, it is. Strictly speaking I saw the `it` case I encountered. The case...

Consecutive `allow(Foo).to receive(:bar).and_return(baz)` limiting offenses to only should eliminate cases of unintended violations and automatic modifications, so it may be a good to change it that way. WDYT? The following...

Now I'm rethinking whether I really need this Cop. As mentioned in the comments below, it may not be extracted to a separate file for smaller internal classes, and since...

In the following case, I often use [rspec-request_describer](https://github.com/r7kamura/rspec-request_describer) to write a request spec. So in the case of String, I don't think it will necessarily match the file path. WDYT?...

[rspec-request_describer](https://github.com/r7kamura/rspec-request_describer) is a plugin for RSpec, but it is useful to use it as follows, but if you use such a plug-in, it may not be a big problem because...

memo) `RSpec/Capybara/FeatureMethods` is a cop belonging to rubocop-rspec - https://github.com/rubocop/rubocop-rspec/blob/master/lib/rubocop/cop/rspec/capybara/feature_methods.rb

This one seems better to suggest using `file_fixture` now. https://relishapp.com/rspec/rspec-rails/v/3-5/docs/file-fixture And I think this one would be better named `RSpec/Rails/FileFixture`.

@jprince ping :-)

In this connection, the following problems also exist We have the following code: ```ruby File.join(Rails.root.join('app', 'models').to_s, 'user.rb') ``` Run `bundle exec rubocop -A --only Rails/FilePath`. Expected behavior: ```ruby Rails.root.join('app', 'models',...

It might be a good to implement cops related to [Capybara::Minitest::Assertions](https://www.rubydoc.info/gems/capybara/Capybara/Minitest/Assertions) and [Capybara::Minitest::Expectation](https://www.rubydoc.info/gems/capybara/Capybara/Minitest/Expectations) as `Capybara/Minitest` department cops in a similar way to the proposed `Capybara/RSpec` department.