The impetus for this rule is to have a blank line to denote that an asynchronous function call might occur. One case in which it's guaranteed that there's no async business is in a getter. It would be very convenient, in particular for static class getters, to have an option to allow one-liners there.

Here's an example,

// Allowed
const MyClass = class {
    static get name() {
        return 'MySpecialClass';
    }
};

// Allowed
const MyClass = class {
    static get name() { return 'MySpecialClass'; }
};

// Still not allowed
const fn = function () {
    return 'someValue';
};

Apologies in advance for what is most likely a stupid question :)

I'm having trouble finding how to set the allow-one-liners option in .eslintrc. I tried the following among other things with no luck:

{
    "extends": "hapi",
    "rules": {
        "hapi-scope-start": ["allow-one-liners"]
    }
}

Could you point me in the right direct?

Thank you!

Hello,

I like the readability this rule adds to functions with big body, however it does not plays well with arrow functions with implicit return.
Is there any way to configure it ? Le me explain with examples:

const myFn = () => {  // i do like this
   
  code
}

// The linter will complain here:

(x) => x.map( 
                       y => y.someProp
               )

// I am forced to write this instead

(x) => 

    x.map( 
                       y => y.someProp
               )

Please note that the example I provided is simplistic. This is a common patter for me for example while using promises:

(x) => new Promise((resolve,reject) => {
    // some code here
}

Regards

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.