Add no-default-case rule to disallow default cases in switch statements #33
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 pull request introduces a new ESLint rule,
no-default-case, which enforces the absence ofdefaultcases inswitchstatements. This is particularly useful for codebases that rely on exhaustive case handling, such as those using TypeScript's exhaustiveness checks. The rule is configurable to optionally allow empty default cases. The change includes documentation, tests, and integration into the plugin's recommended configuration.New Rule Addition:
src/rules/no-default-case.jsto disallow default cases inswitchstatements, with an option to allow empty default cases.Documentation Updates:
docs/rules/no-default-case.mdto describe usage, options, and rationale for the new rule.README.mdto listno-default-caseunder "Possible Errors" rules.Configuration Changes:
switch-case/no-default-casein the plugin'srecommendedconfiguration insrc/index.js.Testing:
no-default-caseintests/src/rules/no-default-case.js, covering valid and invalid scenarios, including theallowEmptyoption.