Re: [elm-discuss] Help with migrating to the new elm-lang/http.

Excellent article! I think it should end up in elm-community documentation. one small stylistic idea: I like the update in the form I've seen Evan do it with the Result unpacked update : Msg -> Model -> ( Model, Cmd Msg ) update action model = case action of Show -> (

Re: [elm-discuss] Cmd.andThen

Hmm. I want to say it's an issue with the library, but fixing it would involve changing a fair amount of code and using the low level Websocket API. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop

Re: [elm-discuss] Ducked Inference

I think Matz is taking the 'compiler as assistant' idea to a logical conclusion. You know, the idea that compilers/interpreters shouldn't barf at you, but give you a helping hand to write your code, which is where Elm is at also! The thing is, I find it hard to how how this could work well in

Re: [elm-discuss] Cmd.andThen

An example of a library that doesn't expose tasks is the Phoenix Socket library. I had a coworker ask me about sequencing joining a channel, pushing a message and waiting for a reply, and then leaving the channel. Without Tasks being exposed and without Cmd.andThen, that leaves one building the

Re: [elm-discuss] Ducked Inference

It's an interesting perspective, but Matz is doing what's right for ruby. Ruby is dynamically typed; Elm is statically typed. Ruby is mature and has a lot of users counting on stability; Elm is pre-1.0 and has a smaller, more adventurous user base. Granted we have upgrade guides and elm-format

Re: [elm-discuss] Inter triplets communication.

@Nick "triplet" is commonly used shortcut for model, update, view functions. https://www.youtube.com/watch?v=LCNs92YQjhw=youtu.be=21m09s @Richard Thank you for your response, I really appreciate it! As I said before, I can be totally wrong. Put another way, *Elm does not have anything

Re: [elm-discuss] Anyone using Firebase 3.0 with Elm 0.17?

I'm available to help with test and documentation. Cheers On Wednesday, August 17, 2016 at 4:29:49 AM UTC-7, Thomas Weiser wrote: > > I have sketched an API for an effect manager module and will discuss it > soon with you all. > > First I will target Firebase's existing realtime database and

Re: [elm-discuss] Cmd.andThen

Http has an escape hatch to get a Task. Other libraries should do the same. Cmd is deliberately simple, with the hard work being done in Task. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving

Re: [elm-discuss] Cmd.andThen

I can't picture how this function would work. Could you give an example of where you would want to use it? Is this just a shortcut around having to make two passes through the update function? On Tue, Nov 29, 2016 at 1:27 PM, Mark Hamburg wrote: > With various libraries

[elm-discuss] Re: Instaslling Elm 0.17 and Elm 0.18 at the same time.

I'm gonna try the npm local install next time. I've been using Docker. I have a base image which provides Elm (from npm) and separate images for the different commands: elm-make, elm-reactor, elm-package, and elm-repl https://hub.docker.com/r/emmanuelrosa/elm-base/ -- You received this

[elm-discuss] Cmd.andThen

With various libraries only returning commands instead of tasks, would it be reasonable to add the following function (and could it be added without going inside of the implementation for Cmd)? Cmd.andThen : (x -> Cmd y) -> Cmd x -> Cmd y The slippery slope is that we end up recreating much of

[elm-discuss] Re: Lazy and VirtualDom questions (repost?)

> > A) > Indeed, Lazy just checks for referential equality (is it the same > javascript object) and not "elm equality". This is kind of important to > know! > model !== { model | state = model.state} > Thanks for this info! It motivated me to give lazy another try (I couldn't make it work for

Re: [elm-discuss] Firebase package - should be an effect module or native module?

Is such a module even necessary? Couldn't you just write a library that uses the existing http library? Then it could be published. On Nov 29, 2016 11:36 AM, "Nick H" wrote: > (I mentioned version 0.16 because I think that is when the native review > process was

Re: [elm-discuss] Firebase package - should be an effect module or native module?

(I mentioned version 0.16 because I think that is when the native review process was officially discontinued, but actually I bet the community packages on the whitelist are older even than that.) On Tue, Nov 29, 2016 at 11:33 AM, Nick H wrote: > There is no process

[elm-discuss] Re: Instaslling Elm 0.17 and Elm 0.18 at the same time.

On Tuesday, November 29, 2016 at 5:05:25 PM UTC, Simon wrote: > > The easy way is to install elm locally to your project - `npm i elm@0.17` > - and then I think elm-make will find it there (and if not, will default to > the system installed version). > Thanks, I didn't know that. -- You

[elm-discuss] Ducked Inference

I am in the middle of watching a video about 'ducked inference' in Ruby https://www.youtube.com/watch?v=1l3U1X3z0CE basically, static type checking / inference without the type annotations. The annotations will be kept in the background for compile time check, documentation or IDE purposes...

Re: [elm-discuss] Inter triplets communication.

Sergii, not every interaction with the "UserInfo" module needs to go through a function called "update". Just because the top-level Elm architecture uses a single update function and a single view function does not mean that you should automatically mirror this setup throughout your program. As

[elm-discuss] Firebase package - should be an effect module or native module?

What if I'm going to write elm-firebase package - should I write it as an effect module or native module to have a chance to be whitelisted? Ed Ilyin -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop

[elm-discuss] Re: Instaslling Elm 0.17 and Elm 0.18 at the same time.

The easy way is to install elm locally to your project - `npm i elm@0.17` - and then I think elm-make will find it there (and if not, will default to the system installed version). (Got the idea from Noah a couple of weeks ago) On Tuesday, 29 November 2016 14:54:06 UTC+1, Rupert Smith wrote: >

[elm-discuss] Help with migrating to the new elm-lang/http.

This write up here is proving very helpful in understanding the new elm-lang/http. Has before and after examples showing how code is changed between 0.17 and 0.18: http://rundis.github.io/blog/2016/haskel_elm_spa_part6.html -- You received this message because you are subscribed to the Google

Re: [elm-discuss] Inter triplets communication.

On Tuesday, November 29, 2016 at 3:27:18 PM UTC, Rupert Smith wrote: > > I think there is a case to be made for a pub/sub message effects module to > become part of the core language though. > I also think Elmq is not ready for publishing yet. Would like to get some input on what features it

Re: [elm-discuss] Inter triplets communication.

On Tuesday, November 29, 2016 at 2:45:36 PM UTC, sergii.k...@zalando.de wrote: > > @Rupert Smith > Can you add a README or provide few examples how to use it properly? > That I can do. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To

Re: [elm-discuss] Inter triplets communication.

On Tuesday, November 29, 2016 at 2:45:36 PM UTC, sergii.k...@zalando.de wrote: > > @Rupert Smith > Your module for pub/sub looks great! I will be useful for a lot of people > like me. I think you should publish it. > Can you add a README or provide few examples how to use it properly? > It

Re: [elm-discuss] Inter triplets communication.

@Rupert Smith Your module for pub/sub looks great! I will be useful for a lot of people like me. I think you should publish it. Can you add a README or provide few examples how to use it properly? @Nick H I also thought about this > type Action = Loaded | UserInfo UserInfo.Action | Ratings

[elm-discuss] Re: Elm post: feedback requested

I liked the iterative process. I even liked the recap at the end (I usually don't like chapter summaries). I appreciate that you gave a warning against trying to optimize early and when to stop optimizing. Some might be tempted to create a helper function for the specific record to reduce the

[elm-discuss] Re: Instaslling Elm 0.17 and Elm 0.18 at the same time.

On Tuesday, November 29, 2016 at 1:54:06 PM UTC, Rupert Smith wrote: > > Perhaps just create a vm or docker container and install elm 0.18 inside > that? > I created a Dockerfile with these installation commands in it: RUN apt-get update && \ apt-get upgrade -y && \ apt-get clean RUN

[elm-discuss] Re: ANN: style-elements v2 published

Thanks everyone! Hey Max! I appreciate the feedback, I've updated the readme with your suggestions ++ some additional notes. And some additional descriptions for the elm-package documentation will be there later today :) You make a good point about renaming `Style.Model`, though I'm going to

Re: [elm-discuss] Re: Elm post: feedback requested

Op dinsdag 29 november 2016 10:25:50 UTC+1 schreef John Orford: > > Just a note - sometimes a little repetition is helpful when learning or > teaching... At least that's what I tell myself when I find I am repeating > myself :) > Fully agree! Hope I made that clear by adding the workflow

[elm-discuss] Re: Elm post: feedback requested

Thanks Max. I've taken out the somewhat repetitive paragraphs, to make the article itself also more compact and readable :) As for using Dict, the exercise basically shows how to extract functions by rolling your own List equivalent of Dict.update. Using Dict from the start would be less clear

Re: [elm-discuss] Re: elm-make: Map.!: given key is not an element in the map

I kept the whole directory : https://github.com/elm-lang/elm-package/issues/254 Le lundi 28 novembre 2016 20:39:33 UTC+1, Nick H a écrit : > > The situation should be much improved now in 0.18. I don't see it > mentioned in the release notes, but from the beta announcement >