RFC: space-in-parens: exception to distinguish between function calls and sub-expression grouping.

I like to use spaces in parentheses when grouping expressions, but not when calling functions, like this:

a = ( 1 + 2 ) * 3;
b(1, 2);

It allows one to visually mark semantically distinct uses of parentheses.

Would you accept a PR that implements this (and the opposite, off course)?

Edit: Thanks, eslintbot. So, a priori, the only unknown to me is whether it is “1. Widely applicable”.

<bountysource-plugin>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[dantman]

Adding to this; space-in-parens seems to be unable to differentiate condition expressions (i.e. if () {}, where, etc…).

This is important since this is a perfectly valid coding style:

function foo(x) {}

if ( y ) {
  foo('x');
}

i.e. never space parenthesis in general, but always space the test in conditions.

[not-an-aardvark]

Thanks for your interest in improving ESLint. Unfortunately, it looks like this issue didn’t get consensus from the team, so I’m closing it. We define consensus as having three 👍s from team members, as well as a team member willing to champion the proposal. This is a high bar by design – we can’t realistically accept and maintain every feature request in the long term, so we only accept feature requests which are useful enough that there is consensus among the team that they’re worth adding.

Since ESLint is pluggable and can load custom rules at runtime, the lack of consensus among the ESLint team doesn’t need to be a blocker for you using this in your project, if you’d find it useful. It just means that you would need to implement the rule yourself, rather than using a bundled rule that is packaged with ESLint.