Restore @typescript-eslint/no-unsafe-argument

[fregante]

Untested, the comment seemed outdated since --strict now produces unknown

[sindresorhus]

and if you pass the error anywhere, it will trigger this rule

This is the important part and I think it's still valid.

[fregante]

That seems correct, but the rule is still valid.

Also I don’t think TypeScript's error types are incorrect (too loose); They are what they are because javascript allows throw 1 and Promise.reject(1). I don't expect them to change for this reason.

Try/catch is annoying, but once I wrote my isErrorObject type guard I forgot all about this particular issue.

[fregante]

On second review, my initial thought about the rule not applying to "unknown" seems correct:

https://typescript-eslint.io/play#ts=4.9.3&sourceType=module&code=DYUwLgBAhhC8EEZoGdoDsCeBYAUABwCcB7AWzzAAooBKXXUSAIzggCYUIBXNAazSIDuaXIVLkKjakA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6Jge1tieQEMAZolp9oAc1gBbRC3RRE0aB2iRwYAL4h1QA&tsconfig=N4KABGBEDGD2C2AHAlgGwKYCcDyiAuysAdgM6QBcYoEEkJemy0eFYDArugDTg2Tsl0AVSIBrIrADuRAJJEAwgEM80ABYA1RY0UAjDGUoAzRakG8AviHNA

The rule doesn't care about passing unknown to function because typescript already does that natively. Right?