Comment by DylanSp
2 years ago
Typescript's exhaustiveness checking can be kind of clunky sometimes, particularly if you have a switch statement that's just causing side effects and not returning a value. Last time I looked at it, I think you had to add a default case with some sort of dummy statement assigning a value to a variable with type `never`; while that's doable, the ergonomics are a bit annoying.
I recall having to add that dummy 'never' branch in the past, but I haven't had to do that in newer projects on recent versions of Typescript.
I just tried it in the online playground. I didn't get any sort of error with one of the cases unhandled. https://www.typescriptlang.org/play/?noFallthroughCasesInSwi...
Hmm. I think this is because in that situation, all cases (including the unhandled one) are "correctly" returning undefined.
I can see that if I made the branch return a string, Typescript will correctly show the "Not all code paths return a value" error
1 reply →