Add no-else-return check
#93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ruchip16
requested review from
ganeshrn,
trishnaguha,
shatakshiiii,
priyamsahoo and
ssbarnea
and removed request for
a team
audgirka
approved these changes
Apr 11, 2023
shatakshiiii
approved these changes
Apr 11, 2023
ssbarnea
approved these changes
Apr 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
no-else-returncheck is a linting error that usually appears when you have an "else" statement immediately following a "return" statement in a function. The check suggests that you should remove the "else" statement and de-indent the code inside it. This ensures that the code inside the "else" block is not executed unnecessarily and will also make the code more concise and easier to read.