Breaking unidirectional data flow principle ?? about android-flux-todo-app

[lgvalle]

Hi @kevinlg, thanks for your comments. It's a very good question.

Unidirectional data flow is a key principle in Flux architecture and I believe one of its mayor strengths. In this example it is preserved as well.

The Dispatcher is the class responsible for emitting events through the app. An Action event and a StoreChange event are conceptually different things, but the implementation is the same: events. So, that is why there is one single class, Dispatcher, emitting either Actions or StoreChange events.

Unidirectional flow is still preserved. It will be broken if we emit Actions from Stores, but this is not happening in this example. Stores only emit StoreChange events, and Actions are only emitted from ActionCreators.

[kevinlg]

Ok, I was considering the dispatcher to be one waypoint on the flow. If you consider it as an event emitter only then your point is valid.

Thanks for answering the question. I think we can close it.