Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Open
connorshea wants to merge1 commit intomain
base:main
Choose a base branch
Loading
fromfix-16263

Conversation

@connorshea
Copy link
Contributor

@connorsheaconnorshea commentedNov 29, 2025
edited
Loading

The original ESLint rule hasallowDefaultCaseForExhaustiveSwitch: true by 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 actuallytrue by default.

…tiveness-check rule.The original ESLint rule has `allowDefaultCaseForExhaustiveSwitch: true` by default.
CopilotAI review requested due to automatic review settingsNovember 29, 2025 07:30
@graphite-app
Copy link
Contributor

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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-hq
Copy link

CodSpeed Performance Report

Merging#16268 willnot alter performance

Comparingfix-16263 (c9ebdf0) withmain (1a58eea)

Summary

✅ 4 untouched
⏩ 41 skipped1

Footnotes

  1. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase,click here and archive them to remove them from the performance reports.

Copy link
Contributor

CopilotAI left a 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.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

Copilot code reviewCopilotCopilot left review comments

@camc314camc314Awaiting requested review from camc314camc314 is a code owner

Assignees

No one assigned

Labels

A-linterArea - LinterC-bugCategory - Bug

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

linter: typescript/switch-exhaustiveness-check allowDefaultCaseForExhaustiveSwitch differs from typescript-eslint

2 participants

@connorshea

[8]ページ先頭

©2009-2025 Movatter.jp