I have a problem with the whole layout namespace of rubocop. Then on top of that there are some rubocop extensions, the rspec one especially, that forces you t

I have a problem with the whole layout namespace of rubocop. Then on top of that there are some rubocop extensions, the rspec one especially, that forces you to write bad, unreadable tests with the worst performance footprints. So unless you are in a company with a good culture where that talk does happen, I would keep rubocop for security sections. In rspec it forces everything in a let, with single expect per test, so you can never check if two things are set to something at the same time