TSConfig: noFallthroughCasesInSwitch, allowUnreachableCode #16667
Conversation
This file contains hidden or 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
github-actions
bot
added
the
linter
bershanskiy
changed the title
queengooborg
approved these changes
Jun 17, 2022
Contributor
queengooborg
left a comment
queengooborg
left a comment
There was a problem hiding this comment.
Seems good to me, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Enable
noFallthroughCasesInSwitch. I find it easier to just use this rule than insert abreak;or a comment// fall throughin everycase. Also, this particular case of fall-through just happens to be easier to read without a fall-through. Also, note that it's possible to disable this rule on a line-per-line basis via a special comment.Set
allowUnreachableCodetofalseto make TS compiler error out on dead code.Test results and supporting details
N/A
Related issues
N/A