Layout/MultilineMethodCallIndentation requesting illogical results

[tenpaiyomi]

I'm not sure if this is something that can realistically be "fixed", but wanted to just point out a scenario where Rubocop was throwing an error regarding Layout/MultilineMethodCallIndentation that is entirely illogical and results in less readable and maintainable code.

---

Expected behavior

I expect Rubocop to enforce Layout/MultilineMethodCallIndentation in a manner that provides clear, concise, logical results for multiline method call indentations, such that the following code would be considered valid:

      expect { post :parse_emails, params: params, format: :json }.to change { Membership.count }.by(0)
                                                                  .and change { Invitation.count }.by(0)
                                                                  .and raise_error(ActiveRecord::RecordInvalid)

Actual behavior

Rubocop expects the indentation to work at the end of each last method call, for each line, cascading down, like so

      expect { post :parse_emails, params: params, format: :json }.to change { Membership.count }.by(0)
                                                                                                 .and change { Invitation.count }.by(0)
                                                                                                                                 .and raise_error(ActiveRecord::RecordInvalid)

Steps to reproduce the problem

See the above code

RuboCop version

1.26.1 (using Parser 3.1.1.0, rubocop-ast 1.16.0, running on ruby 3.1.1 x86_64-linux)
  - rubocop-faker 1.1.0
  - rubocop-performance 1.12.0
  - rubocop-rails 2.14.2
  - rubocop-rspec 2.9.0

[tenpaiyomi]

Thanks everybody, I greatly appreciate the work you all do.