TypeScript Users: How often do you encounter implicit any introduced by the type system? Not the introduction by user code, but the type system returning any for something it shouldn’t.
-
-
Replying to @sebmck1 reply 0 retweets 1 like
-
Not at all, thanks to --noImplicitAny!
1 reply 0 retweets 11 likes -
To elaborate on that, I would recommend enabling --strict to get the most value out of TypeScript’s type system. I’m a fan of as much strictness as possible. This is usually easier to achieve in greenfield projects but worth working towards to in projects being migrated from JS.
2 replies 0 retweets 16 likes -
I'd recommend against that as it will make it much harder to write the code especially when you use a lot of 3rd party dependencies. Most of the types can safely be casted to any.
2 replies 0 retweets 0 likes -
Replying to @UsuallySarcasm @mariusschulz and
I use strict mode and never had any issues. Most libraries have type definitions and if some don't, I write the definitions for the APIs I'm going to use. It's a bit more work, but worth it for the DX improvement and typesafety.
1 reply 0 retweets 1 like -
Replying to @satya164 @mariusschulz and
"I use X and never had issue" is always an irrelevant argument. Most of the libraries actually do not have definitions or are outdated. If there are definitions we both can use them, but I will not care that much if there are not.
1 reply 0 retweets 0 likes -
Replying to @UsuallySarcasm @mariusschulz and
You're also basing your opinion on your experience :)
1 reply 0 retweets 0 likes -
Replying to @satya164 @mariusschulz and
If you don't find an issue it does not prove its non-existence. If I find an issue it does prove its existence. Basic propositional calculus.
1 reply 0 retweets 0 likes
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 