Back when two-way binding was popular computed properties seems like another confusing layer
-
-
Replying to @jlongster @wycats
#3 would be better if cWRP had a more reduce-y API where you return a value. Then it would be more obvious how to compose it.
3 replies 0 retweets 4 likes -
Replying to @dan_abramov @jlongster
It's nicer to pull values when you need them than to reduce eagerly into one value, I think.
2 replies 0 retweets 2 likes -
Replying to @wycats @dan_abramov
At this point I think the most important thing is consistency: however you do it all of the app works that way (mixing them = worst of both)
1 reply 0 retweets 1 like -
Wait I thought cWRP *just* to help interop w/ 3rd party, non-react utilities? Isn't manually updating state from props in cWRP anti-pattern?
2 replies 0 retweets 0 likes -
Replying to @AdamRackis @jlongster and
Interop would be done in either componentDidUpdate or componentWillUpdate; Heard mixed signals about which one to use :P
1 reply 0 retweets 0 likes -
Replying to @dralletje @AdamRackis and
Wouldn't third party interop be entirely in post-DOM hooks?
1 reply 0 retweets 0 likes -
Replying to @wycats @dralletje and
I think
@ryanflorence is the only one who truly knows when to use cWRP :) iirc it's to "prep" (3rd party) stuff for update.2 replies 0 retweets 0 likes -
Replying to @AdamRackis @dralletje and
Incidentally I cargo culted these prop hooks in Ember and regret it. Wanna deprecate.
1 reply 0 retweets 0 likes -
Replying to @wycats @dralletje and
Even the cDU hook? Surely you need that for 3rd party integration?
1 reply 0 retweets 1 like
cDU is not a prop hook so yeah. That's the one I'd keep. cDM, cDU + one way data flow using tracked getters. (didRender cDM or cDU is
too)
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.