I'm shocked at how often I run into problems due to TypeScript's generous usage of `any` in the standard library definitions. `unknown` is much more appropriate. The promotion of escaping type safety in such a fundamental place is worrying.
It's only the exception because it's hard to do without a validation library, deficiencies in TypeScript refinements, and there not being a strong culture for it
-
-
[No one is doing this because no one wants to do it] seems like a self-defeating argument? The vast majority of JS code trusts the result of JSON.parse follows the schema the server said it would; very few devs want to ship client code to validate that the server isn't broken
-
What I'm saying is I want to do it, so I'm going to do it, and I will make it easier for others to do it, so more people do it, until hopefully everyone does it.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 