Style/HashExcept: Nonequivalent suggestion when using the second, value param of a reject block

[theblang]

The Style/HashExcept rule wants to turn:

{ foo: 1, bar: 2, baz: 3 }.reject { |_, v| [1, 2].include?(v) }

into the nonequivalent

{ foo: 1, bar: 2, baz: 3 }.except(1, 2)

---

Expected behavior

Perhaps nothing, since we're using the second, value param of the reject block. All of the examples show using the first, key param.

Actual behavior

rubocop and rubocop -a want to suggest { foo: 1, bar: 2, baz: 3 }.except(1, 2)

Steps to reproduce the problem

• Paste the code: { foo: 1, bar: 2, baz: 3 }.reject { |_, v| [1, 2].include?(v) }
• Run rubocop -a
• See the code changed to: { foo: 1, bar: 2, baz: 3 }.except(1, 2)

RuboCop version

1.32.0 (using Parser 3.1.2.0, rubocop-ast 1.19.1, running on ruby 3.1.2 x86_64-linux-musl)