Support expect_offense template arguments

[biinari]

Pass keyword arguments through to RuboCop::RSpec::ExpectOffense#expect_offense. These are used to set template replacements like %{name} added in rubocop #8069.

Allow code offense templates in specs to use %{name}. Style/FormatStringToken prefers %<name>s to %{name} but expect_offense does not use Kernel#format or String#%.

Example usage (from work in progress for #992):

[include_examples it_behaves_like it_should_behave_like].each do |include_method|
  it "registers an offense with #{include_method}" do
    expect_offense(<<~RUBY, include_method: include_method)
      describe 'foo' do
        %{include_method} 'an x'
        ^{include_method}^^^^^^^ Repeated include of shared_examples 'an x' on line(s) [3]
        %{include_method} 'an x'
        ^{include_method}^^^^^^^ Repeated include of shared_examples 'an x' on line(s) [2]
      end
    RUBY
  end
end

---

Before submitting the PR make sure the following are checked:

• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Updated documentation.
• Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
• The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

[pirj]

Thanks!

Can you please add an example usage of this feature?

I'm not sure I completely understand why FormatStringToken should be disabled for cops.

The feature was released as part of RuboCop 0.85, and we depend on 0.87+, so 👍

[biinari]

No problem @pirj. I've added an example and a bit more explanation for the disabling of the Style/FormatStringToken cop. I'm making use of this in the specs for #992, which I'll finish off later.

[pirj]

Thank you!