Got it, thanks, Witold.
This version is more direct without the need for an alias.
deletePlayer : Player -> Cmd Msg
deletePlayer player =
restRequest (hostUrl ++ "/players/" ++ (toString player.id))
(playerEncode player)
(Json.Decode.succeed player)
DELETE
|>
I was quite disappointed to see that signals have been removed in Elm 0.17
(I found out about elm 6 days ago). I only seen a few bits of code using
signals from before which had very simple `merge`/`map`/`filter`/and the
notorious `foldp` operations. But I think signals & current implementation
On Tuesday, March 7, 2017 at 12:54:50 AM UTC, Joey Eremondi wrote:
>
> Now, you could do something where you have a working version of your code,
> and you generate a set of tests and save it, and then use it as regression
> tests later on to make sure you don't accidentally change the behaviour
On Tuesday, March 7, 2017 at 4:28:52 AM UTC, Matthieu Pizenberg wrote:
>
> Hi everyone,
>
> I would like to have the point of view of the community regarding some
> private/public types code organisation. I have some types very useful to
> many sub modules that are currently publicly exposed in
It's easy to find concrete issues - a whole class of issues would be solved
with task ports.
All problems that require interop between Elm and JS, where a message from
Elm to JS must be correlated with a message from JS to Elm. The async
request-response pattern. Like callbacks or Promises in
