You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In TS 4.4, useUnknownInCatchVariables is activated by default if you have it configured to strict: true. Which is a good practice.
This makes the caught variables in a try/catch block to be of the unknown type, so we need to check if the object we are catching is an error in our try/catch blocks to comply with this new rule.
In #567, TS got updated to 4.4 along with other dependencies to make the React 18 tests pass; the mentioned config option is explicitly deactivated until we adapt our try/catch blocks.
In TS 4.4,
useUnknownInCatchVariables
is activated by default if you have it configured tostrict: true
. Which is a good practice.This makes the caught variables in a try/catch block to be of the
unknown
type, so we need to check if the object we are catching is an error in our try/catch blocks to comply with this new rule.In #567, TS got updated to 4.4 along with other dependencies to make the React 18 tests pass; the mentioned config option is explicitly deactivated until we adapt our try/catch blocks.
Official docs: https://www.typescriptlang.org/tsconfig#useUnknownInCatchVariables
TODO
The text was updated successfully, but these errors were encountered: