Flag to type `Promise.catch` variables as `unknown`

Suggestion

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Following #41016 a flag was added to consider catch variables as unknown.
For consistency and since they're similar cases, I suggest also adding a flag that does this for .catch callbacks on promises.

See also: eslint-plugin-etc/no-implicit-any-catch

L’issue ne mentionne aucun fichier du dépôt ni aucun test. Commencez par lire la modification existante des variables catch référencée dans #41016, puis comparez-la au comportement des callbacks de Promise.catch et à la règle eslint associée. Le travail est terminé lorsqu’un design de flag révisé ainsi que l’implémentation et les tests correspondants typent ces variables de callback comme unknown.