Re: [elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

Using elm-webpack-starter means that the process is slightly different from the guide. In the guide, you build elm.js and edit some index.html which has a script tag where you start the Elm app add work with the ports. Using the elm-webpack-starter you have the src/static/index.js where the Elm

Re: [elm-discuss] Uri encoding (Implementing /Programming Phoenix/ with Elm web sockets)

Should anyone be interested, I wrote up how to use Elm websockets in a way that matches the exposition in /Programming Phoenix/: http://stackoverflow.com/questions/40475348/how-do-i-pass-connection-time-websocket-parameters-to-phoenix-from-elm > On Nov 6, 2016, at 7:09 PM, Brian Marick

[elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

No one? If the recommended solution is to move off webpack (plus pointers to a replacement) that's fine too; I would just like to get my dev environment set up once and for all and then go back to writing elm code. martin On Sat, Nov 5, 2016 at 5:31 PM, Martin DeMello

[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

On Tuesday, November 8, 2016 at 2:45:26 AM UTC+11, Ian Dickinson wrote: > > >> With respect, I'm not sure that the essence of JS fatigue is new features > of the language itself, although I suppose ES5 to ES2015 is quite a big > change. As I hear it, it's rather the explosion of build tools,

[elm-discuss] Re: Fetch an element in a list from a parent module and render it in a child module

With multi-selection, I put a `selected : Bool` on the item itself. When you reload a list, you can just default it to false. On Monday, November 7, 2016 at 12:01:26 PM UTC-6, Rickey Barnes wrote: > > That sounds like a better way than what I was thinking. Although I don't > think it would work

Re: [elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

I think *convincing* is besides the point. Tech comes and goes. I would rather read through the features of Elm, and make a checklist. Pure functions Immutability ADTs Explicitness (avoiding type classes and other abstractions) User friendliness ... If your team buys into these features, then

[elm-discuss] Re: Fetch an element in a list from a parent module and render it in a child module

That sounds like a better way than what I was thinking. Although I don't think it would work if you wanted to show multiple detail sections. For example if you clicked on 2 different contacts, but you didn't want the previous details to disappear with the new selection. -- You received this

[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

Just a few comments: > The one thing I'm not really sure I'm prepared to answer is how I can be sure that Elm isn't just another CoffeeScript or Dart, and in 2 or 3 years we'll have an impossible time hiring anyone > > who knows how to use it because everyone's going to go back to JavaScript.

Re: [elm-discuss] How do you test a TEA `update` function?

See, for example, here: https://groups.google.com/forum/#!topic/elm-discuss/qhLsLThplUo An approach in which one waits "longer" to convert requests to commands appears to be more readily testable. (That said, I haven't taken to writing unit tests yet for this code and while one can compare for

[elm-discuss] Re: Fetch an element in a list from a parent module and render it in a child module

If you do it that way you would also have to generate unique Ids for each contact somewhere in your update function. And I assume your new render function would take 2 inputs now? -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe

[elm-discuss] Re: Fetch an element in a list from a parent module and render it in a child module

What I've done is this: - Change the Model to have selectedContactId - Change renderContact to also take in the currently selected ID |> List.map (renderContact model.selectedContactId) The renderContact function can check if the selectedContactId is equal to the current item's ID

[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

On Sunday, November 6, 2016 at 8:49:07 PM UTC, Francesco Orsenigo wrote: > > > CoffeeScript and Elm address two vastly different problems. > > CoffeeScript addressed "Writing JS is a pain in the ass": it was syntactic > sugar and the need for it drastically lessened with ES6. > CS was killed by

[elm-discuss] Re: Fetch an element in a list from a parent module and render it in a child module

Hi, Not sure if you still have this problem, or even if I understood your problem (I'm brand new to Elm so please be gentle), but I tried something similar a few days ago so I figure my solution might help a bit. As I understand (please correct me if I misread), you want to show/hide a

[elm-discuss] Re: Best place to find elm devs?

Best place to find them: make them. Hire candidates who show promise and give them some time to train on Elm. It's pretty easy to learn and pretty forgiving to refactor. On Friday, November 4, 2016 at 6:04:05 PM UTC-5, aar...@enfluid.com wrote: > > Hi there! > > I’m here to ask what's the best

Re: [elm-discuss] Re: Metalinguistic abstractions over databases

Okay awesome. Thanks so much! On Fri, Nov 4, 2016 at 7:54 PM, OvermindDL1 wrote: > Ah, no, in fact I do not recall seeing that, it looks like it has had a > lot of development recently so it appears that it might be newer than when > I built my api pipeline. I've not had

[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

On Saturday, November 5, 2016 at 10:01:42 PM UTC, Zacqary Adam Xeper wrote: > > The one thing I'm not really sure I'm prepared to answer is how I can be > sure that Elm isn't just another CoffeeScript or Dart, and in 2 or 3 years > we'll have an impossible time hiring anyone who knows how to use

Re: [elm-discuss] Re: How do you test a TEA `update` function?

This is an area I've been a little uncomfortable with. There seems two be a couple of options though: 1) https://github.com/avh4/elm-testable - I haven't used it but it seems that it provides replacement commands that you can run assertions against. This approach seems limited as it only

Re: [elm-discuss] Re: How do you test a TEA `update` function?

... which is ironic given all emphasis on 'effects as data' On Monday, 7 November 2016 09:51:56 UTC+1, Austin Bingham wrote: > > I asked more or less the same question about a month ago and got no > responses: > > >

Re: [elm-discuss] Re: How do you test a TEA `update` function?

I asked more or less the same question about a month ago and got no responses: https://www.reddit.com/r/elm/comments/593vua/how_to_test_the_complete_update_cycle/ https://groups.google.com/d/msg/elm-discuss/634UXiZjRFQ/lVeDED1oBQAJ The only practical answer right now seems to be to use