These are chat archives for reflux/refluxjs

15th
May 2015
Gabe Medrash
@GabeMedrash
May 15 2015 18:51
If I can use Reflux.connect(...) from within any component, is there a particular reason why I would listen to store changes at the "top" of my app (e.g., my root app component) and then pass that state down throughout my app through props instead of just subscribing to changes from within only those child components that depend on particular stores?
Matt Wean
@mwean
May 15 2015 20:28
@GabeMedrash I have that same question. It seems overkill to pass everything down, so I'm subscribing in whatever component needs it
Gabe Medrash
@GabeMedrash
May 15 2015 20:51
@mwean It seems like the "React way" is to pass everything down, but I don't really see how that makes an app any simpler to reason about over just declaring that a component listens to a store. As a matter of fact, I think listening to a store makes a component much simpler to reason about and extend, considering that you don't have to continually pass props down from parent to child.
Matt Wean
@mwean
May 15 2015 20:57
I think passing things down is supposed to help with one-way data flow
So if we're using flux, it shouldn't be needed