chore: resolve remaining switch-exhaustiveness-check warnings#7113
Draft
isaacroldan wants to merge 1 commit into03-26-chore_fix_87_eslint_warnings_across_the_codebasefrom
Conversation
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
isaacroldan
force-pushed
the
03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings
branch
from
219a35f to
5617f2f
Compare
isaacroldan
force-pushed
the
03-26-chore_fix_87_eslint_warnings_across_the_codebase
branch
from
5965a70 to
351844e
Compare
Fix all 20 remaining eslint warnings (switch-exhaustiveness-check): - fqdn.ts: file-level suppress — all switches branch on 'local' vs default (production). Tests mock serviceEnvironment() returning undefined, so explicit enum cases break tests. - scopes.ts: add explicit 'admin'|'storefront-renderer' cases that throw - output.ts: add missing 'silent' case to logLevelValue - tree-kill.ts: suppress — default handles all Unix-like platforms - mkcert.ts: suppress — default throws for unsupported platforms - Logs.tsx: replace default with explicit BackgroundExecutionReason.Unknown - execute-bulk-operation.ts: replace default with explicit error status cases - format-bulk-operation-status.ts: replace default with explicit status cases - extension.ts: replace default with explicit undefined|liquid|config-only - declarative-definitions.ts: replace defaults with explicit GraphQL enum cases - extension-config-builder.ts: replace default with explicit undefined case, use ?? instead of || for context fallback chain Combined with the parent PR, this brings the codebase from 107 warnings to 0. Co-authored-by: Claude Code <claude-code@anthropic.com>
isaacroldan
force-pushed
the
03-26-chore_fix_87_eslint_warnings_across_the_codebase
branch
from
351844e to
d167d8f
Compare
isaacroldan
force-pushed
the
03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings
branch
from
5617f2f to
b348343
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
WHY are these changes introduced?
Fixes #0000
WHAT is this pull request doing?
How to test your changes?
Post-release steps
Measuring impact
How do we know this change was effective? Please choose one:
Checklist