-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: enable useUnknownInCatchVariables TypeScript option #494
Conversation
This enables the [useUnknownInCatchVariables] TypeScript option, bringing a little more type safety. I fixed a few violations, in part by moving `isRecord` to its own file with tests. [useUnknownInCatchVariables]: https://www.typescriptlang.org/tsconfig/#useUnknownInCatchVariables
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nothing blocking but added some thoughts
Co-authored-by: Andrew Chou <andrewchou@fastmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the isRecord()
implementation can be completely removed now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my bad, didn't realize isRecord() existed for other parts of the codebase prior to this PR
It looks like it's still needed but only by one place now, so I've moved it back in aaf0af5. |
This enables the useUnknownInCatchVariables TypeScript option, bringing a little more type safety.
I fixed a few violations, in part by moving
isRecord
to its own file with tests.