feat(eslint-plugin): [explicit-function-return-type] add option to allow concise arrows that start with void #1732
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an option to complement the
no-void
base rule allowing the use ofvoid
in the same conditions.Since that issue is still being evaluated, I've not made any reference to it, but the use-case is still valid even if the team decide against it.
The idea is to not require you to double up
void
:This change means that an option can be enabled that allows you to drop the
void
return type:This is only allowed when the option is enabled and: the arrow function is concise, and starts with the
void
operator.I'm completely open to bikeshedding on the name & such - I just didn't feel it was worth an issue given how small it is to implement, and makes more sense seeing it visually.