-
-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(linter): friendly diagnostic messages for no-else-return
#6349
Merged
graphite-app
merged 1 commit into
main
from
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
Oct 8, 2024
Merged
fix(linter): friendly diagnostic messages for no-else-return
#6349
graphite-app
merged 1 commit into
main
from
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
Oct 8, 2024
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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
DonIsaac
added
the
C-enhancement
Category - New feature or request
label
Oct 7, 2024
— with
Graphite App
CodSpeed Performance ReportMerging #6349 will not alter performanceComparing Summary
|
DonIsaac
changed the base branch from
don/10-07-fix_linter_no_else_return_fixer_fails_when_else_has_no_trailing_whitespace
to
graphite-base/6349
October 7, 2024 23:19
DonIsaac
force-pushed
the
graphite-base/6349
branch
from
October 7, 2024 23:24
1ade3c3
to
71ad5d3
Compare
DonIsaac
force-pushed
the
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
branch
from
October 7, 2024 23:24
40f966f
to
9991923
Compare
DonIsaac
force-pushed
the
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
branch
from
October 7, 2024 23:25
9991923
to
63f1622
Compare
Merge activity
|
### Before ``` ⚠ eslint(no-else-return): Unnecessary 'else' after 'return'. ╭─[no_else_return.tsx:1:48] 1 │ function foo1() { if (true) { return x; } else { return y; } } · ───────────── ╰──── help: Replace ` else { return y; }` with ` return y; `. ``` ### After ``` ⚠ eslint(no-else-return): Unnecessary 'else' after 'return'. ╭─[no_else_return.tsx:1:31] 1 │ function foo1() { if (true) { return x; } else { return y; } } · ────┬──── ───┬── · │ ╰── Making this `else` block unnecessary. · ╰── This consequent block always returns, ╰──── help: Remove the `else` block, moving its contents outside of the `if` statement. ```
Boshen
force-pushed
the
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
branch
from
October 8, 2024 01:27
63f1622
to
00df6e5
Compare
graphite-app
bot
deleted the
don/10-07-fix_linter_friendly_diagnostic_messages_for_no-else-return_
branch
October 8, 2024 01:31
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0-merge
Merge with Graphite Merge Queue
A-linter
Area - Linter
C-enhancement
Category - New feature or request
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.
Before
After