Loosen @typescript-eslint/switch-exhaustiveness-check rule to allow default case

[Mrtenz]

@typescript-eslint/switch-exhaustiveness-check checks if each case of a switch statement is handled. By default in the case of a union type, each union member must be handled explicitly. This change loosens is a bit, to allow default as well, rather than specifying each union member explicitly. For example, the following is now allowed, but previously was not:

type SomeType = 'foo' | 'bar' | 'baz';
declare const someVariable: SomeType;

switch (someVariable) {
  case 'foo':
    // ...

  case: 'bar':
    // ...

  // Implicitly handles `baz`
  default:
    // ...
}

This required bumping typescript-eslint as well, since this option was added in a more recent version.

[socket-security]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@typescript-eslint/eslint-plugin@8.24.1 🔁 npm/@typescript-eslint/eslint-plugin@8.6.0	None	+4	3.89 MB	bradzacher, jameshenry
npm/@typescript-eslint/parser@8.24.1 🔁 npm/@typescript-eslint/parser@8.6.0	None	+2	787 kB	bradzacher, jameshenry
npm/@typescript-eslint/type-utils@8.24.1 🔁 npm/@typescript-eslint/type-utils@8.6.0	None	0	126 kB	bradzacher, jameshenry
npm/typescript-eslint@8.24.1 🔁 npm/typescript-eslint@8.6.0	None	+1	386 kB	jameshenry

View full report↗︎

[Gudahtt]

LGTM!