proposal:add new option to rule array-callback-return and getter-return

[aladdin-add]

What rule do you want to change?
array-callback-return

Does this change cause the rule to produce more or fewer warnings?
fewer.

How will the change be implemented? (New option, new default behavior, etc.)?
new option:
"allowImplicit": true -- allows implicitly returning undefined with a return; statement.

Please provide some example code that this change will affect:

/* eslint array-callback-return: [2, {allowImplicit: true} */
[1, 2, 3].map(function (item) {
  return; // return undefined implicitly.
});

What does the rule currently do for this code?
Function expected a return value.(array-callback-return)

What will the rule do after it's changed?
no error.

[ljharb]

Yes please - I never write return undefined; because undefined is not a keyword, and is not a safe token to rely on in non-app code.

I would love this option (and would enable it in the airbnb config).

[eslintbot]

Hi @aladdin-add, thanks for the issue. It looks like there's not enough information for us to know how to help you.

Requesting a rule change? Please see Proposing a Rule Change for instructions.

If it's something else, please just provide as much additional information as possible. Thanks!

(edited by @platinumazure)

[platinumazure]

Hi @aladdin-add, are you thinking we should enhance the rule with an option like for getter-return? Or should we just focus on cleaning up the documentation?

[ljharb]

I would like an option.

[aladdin-add]

the rule getter-return's option allowImplicit has been accepted. so better to be consistent.
updated the OP.

[platinumazure]

@ljharb You could use return void 0;, that's perfectly safe.

That said, I'm 👍 to there being an option.

[platinumazure]

@eslint/eslint-team A PR just came for this, we should probably evaluate quickly or else close.

[ilyavolodin]

@eslint/eslint-team Does anyone else want's to support this change?

[kaicataldo]

From the original post by @aladdin-add:

"allowImplicit": true -- disallows implicitly returning undefined with a return; statement.

Just to clarify, should this actually read like this?

"allowImplicit": true -- disallows allows implicitly returning undefined with a return; statement."`

[aladdin-add]

eh.yes! corrected @kaicataldo

[ilyavolodin]

Marking as accepted since @aladdin-add is part of the team and will be the champion.