Not sure if they were added FOR react or they just use the features in the react types.
-
-
I just happened to learn a ton by going through the type definitions for React in the Flow repo.
1 reply 0 retweets 0 likes -
Replying to @naman34
fwiw Ember has the same .get issue, and this is an elegant solution. I'll ask the TS folks if it's particularly hard.
2 replies 0 retweets 1 like -
Replying to @wycats
I think the Flow team was willing to make exceptions and add some magic types. Not particularly hard to do I would think.
2 replies 0 retweets 0 likes -
pre-processing is a big win for TS on the other hand. Not sure how to plug that into IDE tools though.
1 reply 0 retweets 0 likes -
Replying to @naman34
TS and VSCode would need to support procedural macros in the type language. Seems hard... :P
1 reply 0 retweets 0 likes -
Replying to @wycats
I think a plugin system for TS like Babel would be awesome!
2 replies 0 retweets 0 likes -
easier just to add support for TS in Babel, why duplicate an ecosystem
1 reply 0 retweets 1 like -
TypeScript in TypeScript is just a great thing. And I doubt babel will want to implement in TS :)
2 replies 0 retweets 1 like -
Replying to @wycats @thejameskyle
there's also that language service thing which is important for tools
1 reply 0 retweets 1 like
indeed. Any plugins have to work directly with TypeScript so VSCode can understand what's going on.
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.