Skip to content

use unknown instead of any #1666

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.

Sign up for GitHub

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

Jump to bottom
Closed
tomholub opened this issue Apr 20, 2019 · 2 comments
Closed

use unknown instead of any #1666

tomholub opened this issue Apr 20, 2019 · 2 comments
Assignees
@tomholub
Milestone
6.7.5: Deprecatin...

Comments

@tomholub
Copy link
Collaborator

It would be safer to use unknown instead of any everywhere, I'll make another issue.

Originally posted by @tomholub in #1657 (comment)
@tomholub tomholub added this to the 6.7.5 milestone Apr 20, 2019
@tomholub tomholub self-assigned this Apr 20, 2019
@tomholub tomholub changed the title It would be safer to use unknown instead of any everywhere, I'll make another issue. use unknown instead of any Apr 20, 2019
tomholub pushed a commit that referenced this issue Apr 20, 2019
errors unknown type | #1666
086487a
@tomholub
Copy link
Collaborator Author

Unfortunately running into microsoft/TypeScript#26174

tomholub pushed a commit that referenced this issue Apr 20, 2019
Revert "errors unknown type | #1666"
e30c586 
This reverts commit 086487a.
@tomholub
Copy link
Collaborator Author

TypeScript is always returning any from catch blocks and this is not configurable, so switching everything to unknown is not convenient until microsoft/TypeScript#26174 is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomholub tomholub

Labels
None yet
Projects
None yet
Milestone
6.7.5: Deprecating attests
Development

No branches or pull requests
1 participant
@tomholub