Should I put logic into ActionCreators? about flux

[fisherwebdev]

You can put logic in an ActionCreator, but often there is a better design.

"Calculate and apply a route which brings this resource to that target"

Is this in response to a user interaction with the UI?

If so, I would try to do as much logic as possible in the stores, perhaps utilizing Dispatcher.waitFor(), and pass those values down as props to the view. In an event handler, the view would only apply the user-driven variables against those precalculated values that were passed down, and then call the appropriate ActionCreator with the parameters it needs.

If this is in response to another action, I would back up and look at how I am handling that action. I would gather all the required information, again possibly with waitFor(), to "apply a route..." in response to that original action.