Skip to content

chore: resolve remaining switch-exhaustiveness-check warnings#7113

Open
isaacroldan wants to merge 1 commit into03-26-chore_fix_87_eslint_warnings_across_the_codebasefrom
03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings
Open

chore: resolve remaining switch-exhaustiveness-check warnings#7113
isaacroldan wants to merge 1 commit into03-26-chore_fix_87_eslint_warnings_across_the_codebasefrom
03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings

Conversation

@isaacroldan
Copy link
Contributor

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:

  • n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
  • Existing analytics will cater for this addition
  • PR includes analytics changes to measure impact

Checklist

  • I've considered possible cross-platform impacts (Mac, Linux, Windows)
  • I've considered possible documentation changes

Copy link
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.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@isaacroldan isaacroldan force-pushed the 03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings branch from 219a35f to 5617f2f Compare March 26, 2026 15:26
@isaacroldan isaacroldan force-pushed the 03-26-chore_fix_87_eslint_warnings_across_the_codebase branch 2 times, most recently from 351844e to d167d8f Compare March 26, 2026 18:07
@isaacroldan isaacroldan force-pushed the 03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings branch 2 times, most recently from b348343 to a45bace Compare March 27, 2026 09:18
@isaacroldan isaacroldan force-pushed the 03-26-chore_fix_87_eslint_warnings_across_the_codebase branch 2 times, most recently from 731c405 to 7d8f828 Compare March 27, 2026 09:26
@isaacroldan isaacroldan force-pushed the 03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings branch from a45bace to d9a2ee6 Compare March 27, 2026 09:26
@github-actions
Copy link
Contributor

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 82.28% 15093/18343
🟡 Branches 74.84% 7441/9942
🟢 Functions 81.29% 3794/4667
🟢 Lines 82.67% 14271/17262

Test suite run success

3990 tests passing in 1527 suites.

Report generated by 🧪jest coverage report action from d9a2ee6

@isaacroldan isaacroldan force-pushed the 03-26-chore_fix_87_eslint_warnings_across_the_codebase branch from 7d8f828 to b23df55 Compare March 27, 2026 10:23
@isaacroldan isaacroldan force-pushed the 03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings branch from d9a2ee6 to 62a7259 Compare March 27, 2026 10:23
@isaacroldan isaacroldan marked this pull request as ready for review March 27, 2026 10:24
@isaacroldan isaacroldan requested a review from a team as a code owner March 27, 2026 10:24
@github-actions
Copy link
Contributor

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

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 isaacroldan force-pushed the 03-26-chore_fix_87_eslint_warnings_across_the_codebase branch from b23df55 to ccb06f4 Compare March 27, 2026 10:25
@isaacroldan isaacroldan force-pushed the 03-26-chore_resolve_remaining_switch-exhaustiveness-check_warnings branch from 62a7259 to 4535e02 Compare March 27, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant