I completely disagree. I'm on two separate projects right now. One is a legacy mess of unnecessary if statements where none are required (in Django, but that's not the issue) and the other is one is a Rails project I took over from a reasonable developer.
Rubocop is awesome. The -A flag does the right thing and the lint fixes really do make code easier to read. Even the examples in this post make me even more convinced of Rubocop's awesomeness.
super if safe?(name, attrs)
Seems reasonable to me. If I care about the return value I can check the parent class. The problem with "if statements for readability" is that as the implementation grows so do the if statements. You're pushing state into the program cursor instead of into local variables or data structures. It makes it harder to determine if you have full test coverage and it makes it harder to understand if you've caught every combination.
Rubocop is awesome. The -A flag does the right thing and the lint fixes really do make code easier to read. Even the examples in this post make me even more convinced of Rubocop's awesomeness.
Seems reasonable to me. If I care about the return value I can check the parent class. The problem with "if statements for readability" is that as the implementation grows so do the if statements. You're pushing state into the program cursor instead of into local variables or data structures. It makes it harder to determine if you have full test coverage and it makes it harder to understand if you've caught every combination.