Unable to affect state asynchronously from store, apply component `this` to handler function? about dispatchr HOT 7 CLOSED

In Flux, the store should never have direct access to the component, just like in MVC the models should never reference the views. Any information that you need the store to have access to should be passed to the dispatch() method. The component should only be listening to changes from the store: store.on('change', () => { this.setState(store.getState()); })

from dispatchr.

@mridgway - Am I misunderstanding Promises? It seems that I cannot return the object containing the updates for state from the Promise within GET_STATE, but just another Promise?

from dispatchr.

Stores are EventEmitters, so you have the component add a change listener and when you call this.emitChange() it tells the listener that the store content has changed. Promises are not needed within stores since handlers are completely synchronous.

from dispatchr.

All good points, and appreciated. Although you may notice in the example above that the data being set relies on a Promise being resolved from an asynchronous fetch. So in that case I do still think we need a way to affect state from within the then.

from dispatchr.

Looking at this again, I think I see your point regarding store.on('change', () => { this.setState(store.getState()); })

But if you could please expand on that, as I don't immediately see a way to access ShowsListStore for on() or getState()

But overall I think the point is to fire the action from the component, allow the store to make its async fetch call and update an object property of the store, say stateObj, with the desired state changes, and emit a change. Following that, the component would listen for the store's change and call ShowsListStore.getState() which would be a public method which would return stateObj.

So again, if all that makes sense, it is then a matter of being able to access on() and getState() from ShowsListStore.

from dispatchr.

I was just able to implement the above. Thanks for responding to the issue, and not only reiterating why direct access to the component from the store is an anti-pattern, but clearly outlining a way out.

from dispatchr.

Glad you figured it out @jeromecovington! Sorry for the delay in responses. If you have any other issues you may be able to get faster responses in our #fluxible channel on Reactiflux.

from dispatchr.