We could enable this rule and then adopt a style of using switch statements rather than if/else:

'@typescript-eslint/switch-exhaustiveness-check': 'error',

It should help prevent bugs like COMPASS-9121.

I enabled it for one package here: https://github.com/mongodb-js/compass/pull/6819

But when I tried to enable it everywhere I got a bunch of errors where eslint / ts was suddenly not happy with our config:

@mongodb-js/compass-find-in-page: Error: Error while loading rule '@typescript-eslint/switch-exhaustiveness-check': You have used a rule which requires parserServices to be generated. You must therefore provide a value for the "parserOptions.project" property for @typescript-eslint/parser.
@mongodb-js/compass-find-in-page: Occurred while linting /Users/leroux.bodenstein/mongo/compass/packages/compass-find-in-page/.eslintrc.js

Which was weird because that package already specified parserOptions.project. I must have just set it wrong?