Better RuboCop rules?

[mach-kernel]

I made some changes to the rubocop rules for the project that I want to kick around and see if they make sense:

• MaxNesting -> Max
  • Silence the warning message
• MultipleExpectations
  • I have seen bad tests that place multiple behavioral expectations in one it block, but there exist good arguments for not just universally applying this rule.
• MessageSpies
  • For most test cases I think this one grasps at straws?
• Disable BlockLength in spec directories
  • It is not unreasonable to have a test that is ~100 LoC.

[nijikon]

@mach-kernel Thanks for you PR. If you are doing this for karafka don't waste time on this, we will be dropping support for polishgeeks-dev-tools in favor of https://coditsu.io

[mach-kernel]

@nijikon I did this for the onboarding of Waterdrop to the Coditsu suite. See waterdrop/27 😸

[mensfeld]

@mach-kernel you're alive <3

[mach-kernel]

@mach-kernel you're alive <3

It's great to hear from you. Sorry for disappearing. I'm on Discord as mach_kernel#4830 if you want to get in touch! Hope you guys are all doing well!!!