Max, yeah I understand the Req structure, but I'm not sure what it benefit it would provide with the 401 issue that I'm facing
yeah. Here's the original thread by the way: https://groups.google.com/forum/#!searchin/elm-discuss/authentication/elm-discuss/j-Wa6NGiYUM/mDqWXywXAwAJ I think this entire thread is a roundabout way of me asking about Authentication and managing currentUser state. I think I'll open a new thread instead. On Tuesday, July 5, 2016 at 11:23:11 PM UTC-4, Mark Hamburg wrote: > > 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.
