Here is the general flow with the request system: Instead of returning Cmd msg as part of the update result, modules return Req msg (or List (Req msg) if you don't want to build Req.batch). These get mapped and bubble up just like commands. When they get to the API handler level, however, they get translated into commands that will deliver their results back to the API handler level and get converted into messages to be routed further down the hierarchy just as a command would be.
The API handler level can generate HTTP requests. It can use mocks for testing. Whatever seems appropriate. A similar system could be built for subscriptions. Mark -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
