It's hard to say what's going wrong without looking at actual code, but here are a few anti patterns to look out for:
DON'T use actions like methods or setters.
DO try to think of actions as simple events.
DON'T describe the -effect- of an action in its payload.
DO describe the -cause- of potential effects in the payload, and let your reducers handle the rest.
DON'T think of stores as singletons that you can poke at from the UI.
DO think of stores as convenient "views" into the full history of events in your app.
DON'T use actions as a way of announcing that some piece of state has changed. That's what `subscribe` is for.
Here's a great talk about scaling Flux: https://youtu.be/Dm9NgjR5Jn4
It's hard to say what's going wrong without looking at actual code, but here are a few anti patterns to look out for:
DON'T use actions like methods or setters.
DO try to think of actions as simple events.
DON'T describe the -effect- of an action in its payload.
DO describe the -cause- of potential effects in the payload, and let your reducers handle the rest.
DON'T think of stores as singletons that you can poke at from the UI.
DO think of stores as convenient "views" into the full history of events in your app.
DON'T use actions as a way of announcing that some piece of state has changed. That's what `subscribe` is for.
Here's a great talk about scaling Flux: https://youtu.be/Dm9NgjR5Jn4