IMO there are valid cases where we want to give meaningful names to block arguments.
I'm not against using anonymous blocks per se, so I suggest to disable that cop in our default config.
Vote:
:+1: Disable
:-1: Keep enabled
:confused: Keep enabled, but set EnforcedStyle: explicit
Ruby 3.1 introduced support for anonymous blocks. Rubocop by default enforces the anonymous style, if possible: https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Naming/BlockForwarding
IMO there are valid cases where we want to give meaningful names to block arguments. I'm not against using anonymous blocks per se, so I suggest to disable that cop in our default config.
Vote: :+1: Disable :-1: Keep enabled :confused: Keep enabled, but set
EnforcedStyle: explicit