I guess what you need here is
Task.andThen
http://package.elm-lang.org/packages/elm-lang/core/latest/Task#andThen
See this snippet I've found on
github
https://github.com/fpapado/elm-flickr-gallery/blob/c040f61575f4f47ce216df1820b42d1751ccdb7a/src/Main.elm#L56
Hope it helps.
On Monday,
Josh, this is great! Thanks for this idea
Textfield.onInput <| ProjectMsg' << SetNewProjectName
On Monday, August 29, 2016 at 11:03:12 PM UTC+3, Josh Adams wrote:
>
> Here's what I've been working on. The recent git history is all about
> refactoring. Haven't introduced 'sub-components with
Hi
On Sunday, August 28, 2016 at 2:02:04 PM UTC+3, Wouter In t Velt wrote:
>
> Something I have been struggling with for quite some time (coming from
> React and Flux) is how to scale. There are various posts on this forum
> related to the topic, e.g. Design of large elm apps
>
I've came up with solution very similar to Oliver's :)
Top `Page`(or `Screen`) update functions are getting the `Store` which is a
top level app model. Alternative way is to have `mapToContext` function
that receives some `Props` and `Store` and maps those to some useful
context(it might be
Hi Oliver,
Your code sample looks very similar
to
https://github.com/eirslett/elm-task-port-example/blob/master/example/Main.elm
That's a repo related to proposal on adding `Task-based ports`. They were
proposed more than once already, but I'm not aware of any opinion on the
subject in the
- Interacting with 3rd party libraries that use DOM and have multiple
event-related callbacks
- `Chaining` Cmds and Msgs
- Fighting the lack of interfaces while designing own data structures
On Monday, April 24, 2017 at 5:06:53 PM UTC+3, Jeff Schomay wrote:
>
> Hello,
>
> I am considering doing
