[Question] Form Wizard about flux

[tcoopman]

Problem 1:

Why don't you keep your data/state in a parent component containing both the form and the submit?

Problem 2:

If I'm correct, flux dictates that you should submit to the server with util classes, not in the stores. The util classes can then send an action (succeeded or failure).
If you want to show merged responses, then I think the util class should keep track of requests send and should wait until all request have either failed or succeeded, and then send the action with all results as an argument. Each responsible store can then act on them. The mainstore could check for failed requests and show the popup.

[mtsyganov]

@tcoopman

1. because in the UI the submit button is far far away from content frame
2. Is it ok from architecture point of view to send from store A messages to store B without dispatcher? With dispatcher its not always possible, because sometimes store would send an action while executing another action.

[sterpe]

Sort of violates unidirectional data flow. If you really had to use dispatcher from store you could setImmediate(dispatchfn)

Sent from my iPhone

On Sep 19, 2014, at 5:35 AM, Michael Tsyganov [email protected] wrote:

@tcoopman

1. because in the UI the submit button is far far away from content frame

Is it ok from architecture point of view to send from store A messages to store B without dispatcher? With dispatcher its not always possible, because sometimes store would send an action while executing another action.
—
Reply to this email directly or view it on GitHub.

[sterpe]

It feels like you have a pre-existing system state that is sort of side-effect based then you are trying to model that system with a flux architecture and it's not really working.

Sent from my iPhone

On Sep 19, 2014, at 5:35 AM, Michael Tsyganov [email protected] wrote:

@tcoopman

1. because in the UI the submit button is far far away from content frame

Is it ok from architecture point of view to send from store A messages to store B without dispatcher? With dispatcher its not always possible, because sometimes store would send an action while executing another action.
—
Reply to this email directly or view it on GitHub.

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[kyldvs]

This is stale so closing out. Looking over the examples may be useful to you. There have also been some recent examples that include talking to the server: https://github.com/staltz/flux-challenge/tree/master/submissions/kyldvs