yeah. You can also imagine:
class { @service clock: Clock }
-
-
Replying to @wycats
ooo cool, very Guice esque.
@flowtype@typescriptlang@service1 reply 0 retweets 0 likes -
Replying to @joegaudet @flowtype and
the key here is that the type isn't used by the DI system; just an annotation.
1 reply 0 retweets 0 likes -
Replying to @wycats
hmmm wait, so it doesn’t look for a service of type Clock, just one named clock ?
@flowtype@typescriptlang@service1 reply 0 retweets 0 likes -
Replying to @joegaudet @flowtype and
one named clock, and saying that it's actually a Clock. Should fail to statically type check.
2 replies 0 retweets 0 likes -
Replying to @wycats
sweet! I like the looks of that. Now you just need a JSX option for components and were gtg
@flowtype@typescriptlang1 reply 0 retweets 0 likes -
Replying to @joegaudet
Unfortunately JSX doesn't allow you to do the types of rendering optimizations we're looking to land.
@wycats3 replies 0 retweets 0 likes -
Replying to @joegaudet @tomdale
do you mean things like onclick={{action someMethod}} or {{action 'someAction'}}
2 replies 0 retweets 0 likes -
Replying to @wycats
same with value=“http://foo.bar ”, value seems like a really bad name for that, took me a bit of reading to grok
@tomdale1 reply 0 retweets 0 likes
yeah that was one of the big mistakes with that API. value-path would have been way better
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.