Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork727
fix(linter): Correct the default config options for the switch-exhaustiveness-check rule.#16268
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
…tiveness-check rule.The original ESLint rule has `allowDefaultCaseForExhaustiveSwitch: true` by default.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up usingthis link. An organization admin has enabled theGraphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
CodSpeed Performance ReportMerging#16268 willnot alter performanceComparing Summary
Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Uh oh!
There was an error while loading.Please reload this page.
The original ESLint rule has
allowDefaultCaseForExhaustiveSwitch: trueby default.Fixes#16263.
I don't think this was an intentional decision, as the rule def on the tsgolint side is set to true by default, it's only because of the oxlint rule's defaults that it isn't actually
trueby default.