Standardize arrow functions

[NicoGorr]

Could you please add some rules to arrow functions so the code will be more consistent?

I suggest:
arrow-body-style set to as-needed
arrow-parens set to always
implicit-arrow-linebreak set to beside

Thank you.

[LinusU]

I think this would be great as well, my own code is a total mix between (err) => ... and err => ..., sometimes even in the same project 😆

I'm okay with both, but I think that always having the parenthesis is easier...

[NicoGorr]

Yes, it is. Using parens make the code more consistent.

[LinusU]

Looking at the current eco-system impact of enabling arrow-parens:

"arrow-parens": ["error", "always"]

# tests 271
# pass  246
# fail  25
# violations 696

"arrow-parens": ["error", "as-needed"]

# tests 271
# pass  244
# fail  27
# violations 616

Hmm, this one is very very close.

I'm looking at being able to fetch the full list of packages depending on standard directly from Npm, instead of using our manually sampled list. Perhaps that can shed some more light on it...

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[mightyiam]

'arrow-body-style': ['error', 'as-needed', { requireReturnForObjectLiteral: false }]

Because I've been using the () => ({}) pattern for a long while and I am used to reading it. I like it that way.

'arrow-parens': 'always'. I used to prefer 'as-needed' but since writing so much strict TypeScript, it has been impossible to omit the parens. So yea. 'always'.

I could live with 'implicit-arrow-linebreak': ['error', 'beside']. I could not live with 'below'.

[LinusU]

My vote also goes to 'arrow-parens': 'always'