This does sound like a useful addition. Unlike most of the functions that people suggest adding to core, I don't think Cmd.andThen can be written by an end user (or library author).
On Wed, Nov 30, 2016 at 7:19 AM, Mark Hamburg <[email protected]> wrote: > A bigger issue going forward is that with effects managers, commands > aren't just shims around tasks. So, the notion that a module should expose > both a command-based interface and a task-based interface doesn't hold up > well in the long term. That leads me back to the notion that if commands > are the way to specify work to be done, then they need more of the > facilities that tasks offered. > > That said, I have no idea what Cmd.andThen would do with a batch command. > But are the batches for commands and subscriptions really better than lists? > > Mark > > On Wed, Nov 30, 2016 at 7:12 AM Max Goldstein <[email protected]> > wrote: > >> Austin, you're exactly correct. Cmd is meant to be passed out to the >> runtime, that's it. >> >> The reason Http allows you to skip Task is for learnability. You can make >> a simple request without learning what a Task is. But we shouldn't be >> hobbled by that when we want to compose different types of effects. >> >> -- >> 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. >> > -- > 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. > -- 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.
