Allow padding on simple returns for newline-before-return

ESLint Version: 2.10.1

Problem:

Using newline-before-return with padded-blocks causes a conflict, as padded-blocks insists on padded spacing for functions, and newline-before-return complains if there is a newline before a return statement by itself in a function.

Recommended Solution:

Add an option to newline-before-return to ignore scenarios where the only statement in a function block is the return statement.

For example:

"newline-before-return": ["error", {
    "pad-getters": true  // (New) Ensure getter returns are padded on either side by a newline
}]

This will allow ESLint to properly support it’s built-in plugins without changing the default functionality of the newline-before-return rule. With the above configuration:

This code would result in an error:

function getVar() {
    return this.var;
}

This code would be valid with both plugins:

function getVar() {

    return this.var;

}

[alberto]

I think newline-before-return should not error when it is the first statement in a block, regardless of the newlines and that should be left to padded-blocks.

The doc says (emphasis mine):

This rule requires an empty line before return statements to increase code clarity, except when the return is alone inside a statement group (such as an if statement). In the latter case, the return statement does not need to be delineated by virtue of it being alone.

[markelog]

Can we document what should be considered as breaking change? See JSCS example https://github.com/jscs-dev/node-jscs/blob/master/OVERVIEW.md#user-content-versioning--semver for reference