Chained call expressions are not indented.

What rule do you want to change? indent

Does this change cause the rule to produce more or fewer warnings? Fewer.

How will the change be implemented? (New option, new default behavior, etc.)? New default behavior with new option to configure it.

Examples:

incorrect code

foo
(123)
(456)

correct code

foo
  (123)
  (456)

What does the rule currently do for this code? Chaining function invocations across multiple lines (when permitted by func-call-spacing) expects no indentation.

What will the rule do after it’s changed? Chaining function invocations should be indented by default in the same manner as chaining member method invocations, with the same options for configuration.

foo
  .bar(123)
  .baz(456)

foo
  (123)
  (456)

Are you willing to submit a pull request to implement this change? I am willing to try!

[m59peacemaker]

It’s a critical issue for me, as my primary paradigm is dominated with curried functions that have chained invocations in this way. Single line expressions in this manner are often far worse than the lack of indentation or having to keep the indent rule disabled. Here is a thread about a code style for which multiline call expression indentation is necessary.

[kaicataldo]

This seems like a reasonable enhancement to me - the “correct” example above is what I would expect the rule to enforce by default. Could the option be part of the CallExpression config object? Maybe with the key parenthesis?