EndAlignment method chaining

[lenntt]

I have some interesting code, that doesnt pass the EndAligntment checks (rubocop fails on the do..end blocks):

def foo(bar)
  bar.get_stuffs
      .select {|stuff| stuff.present?}
      .select {|stuff| stuff.attribute == 'whatever'}
      .reject do |stuff| 
        stuff.with_a_very_long_expression_that_doesnt_fit_the_line
      end.select do |stuff|
        stuff.another_very_long_expression_that_doesnt_fit_the_line
      end
      .select do |stuff|
        stuff.another_very_long_expression_that_doesnt_fit_the_line
      end
end

I've tried (as the example shows) both putting the .select on the same line and on the next line.

[bbatsov]

@jonas054 I guess you should tackle this one as well.

[jonas054]

I'd actually like to pass the ball to @edzhelyov. The above code is a good example of the "start of the line where do is" idea that he brought up in #338. OK @edzhelyov?

BTW, even the mighty Emacs has trouble indenting the above code, and the result is less logical than how @SirLenz0rlot did it. It does pass rubocop's inspection though. Here it is:

def foo(bar)
  bar.get_stuffs
    .select {|stuff| stuff.present?}
    .select {|stuff| stuff.attribute == 'whatever'}
    .reject do |stuff| 
    stuff.with_a_very_long_expression_that_doesnt_fit_the_line
  end.select do |stuff|
    stuff.another_very_long_expression_that_doesnt_fit_the_line
  end
    .select do |stuff|
    stuff.another_very_long_expression_that_doesnt_fit_the_line
  end
end

Again, this is by no means better. I just wanted to show it as an example of how complex the problem is.

[jonas054]

The solution for this issue has been removed because we don't want to encourage multiline chaining of blocks. The Ruby Style Guide says that multiline chaining is ugly.