React friends: thoughts on getChildContext? Good? Bad? Ugly?
-
-
Replying to @sebmarkbage
@wycats Something like it is needed to nest high- and low-level abstractions in each other. Can describe it more in detail in person.@leeb2 replies 0 retweets 2 likes -
Replying to @sebmarkbage
@sebmarkbage@leeb but the react community seems harshly negative about them so don't want to dive in too deep too quick :p1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@sebmarkbage not sure why so negative. Maybe because we haven't finalized API so over-abundance of caution.2 replies 0 retweets 0 likes -
Replying to @leeb
@leeb one reason react-router users don't like us to use context is that it adds boilerplate to your tests.@wycats@sebmarkbage1 reply 0 retweets 1 like -
Replying to @mjackson
@leeb maybe it's just that we're a library, i.e. not ok for libs, ok for apps@wycats@sebmarkbage1 reply 0 retweets 1 like
@mjackson @leeb @sebmarkbage agreed. Reusable components don't want to share context with structural components that embedded them.
-
-
Replying to @wycats
@wycats@mjackson@leeb@sebmarkbage context is helpful for talking past unrelated intermediate components instead of leaking impl details.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.