Spaces around function declarations vs. function invocation parens

[jedrichards]

Unless I'm missing it, it seems like a handy rule would relate to spaces around the function keyword parens in different scenarios. Namely, function declaration vs. function invocation. For example:

Enforce spaces around parens for function declarations

// Good
function () {
}
function foo () {
}

// Bad
function() {
}
function(){
}
function foo() {
}
function foo (){
}
function foo(){
}

Enforce no spaces around parens for function invocation

// Good
var a = function();

// Bad
var a = function ();

The rationale behind this rule relates to the fact that some devs like to enforce a visual distinction between a function declaration and a function invocation.

What do you think?

[dsheiko]

Working on formalization of the rules. Does it look fine to you?

{
        "FunctionDeclarationParameterListSpacing": {
            "allowTrailingWhitespaces": 1,
            "allowPrecedingWhitespaces": 1
        },
        "FunctionExpressionParameterListSpacing": {
            "allowTrailingWhitespaces": 1,
            "allowPrecedingWhitespaces": 1
        },
        "CallExpressionArgumentListSpacing": {
            "allowTrailingWhitespaces": 1,
            "allowPrecedingWhitespaces": 1
        },
}

[jedrichards]

Yeah, that looks like it covers things well.

[dsheiko]

Implemented in v.2.1.7

[jedrichards]

Ty :)

[dsheiko]

BTW, you can find these sniffs explained in README.md