Re: [elm-discuss] Re: Task ports: A proposal to make it easier to integrate JS with Elm.

2017-03-06 Thread Tim Stewart
The lack of Task Ports basically lead to me putting Elm on the "watch-list" rather than actively using it on anything. Commands make it too difficult to track interdependencies between multiple separate async operations. I'm glad to see revived interest in this area, hopefully the project

Re: [elm-discuss] Having the debugger write your tests for you

2017-03-06 Thread Will White
Yes, that's what I meant. On Tuesday, March 7, 2017 at 12:54:50 AM UTC, Joey Eremondi wrote: > > The problem I see is that the tests are being generated from the code, so > they'll always pass. > > So, you say you can make a test that update Up 0 == 1. But how did we get > that test? We got 0

[elm-discuss] What about partial public exposition of private types?

2017-03-06 Thread Matthieu Pizenberg
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 a Types module. In order to hide the type implementation, I wonder what you think

[elm-discuss] GSOC 2017

2017-03-06 Thread Akila Wicky
Hi, I am Akila Wickramarachchi and a final year undergraduate student of Department of Computer Engineering, University of Peradeniya, Srilanka. I'm looking forward to participating in GSoC 2017. I have experience in working with Java, Android, Python, Php etc. I have seen the ideas list and I

Re: [elm-discuss] Having the debugger write your tests for you

2017-03-06 Thread Joey Eremondi
The problem I see is that the tests are being generated from the code, so they'll always pass. So, you say you can make a test that update Up 0 == 1. But how did we get that test? We got 0 from the initial value of the model, and 1 from evaluating update Up 0. So if we changed update, or changed

[elm-discuss] Having the debugger write your tests for you

2017-03-06 Thread Will White
The debugger has the model, msg and the new model. So if you tell it that the new model is indeed the expected return value from update msg model, it can write that test for you. To use Counter as an example: model = 0 update msg model = case msg of Up -> model + 1 Down ->

[elm-discuss] Re: Post Examples of Painful Record Updates Here!

2017-03-06 Thread Francesco Orsenigo
@Martin Bailey if I found myself with 50 messages in the model update I'd take as a sign that I need to abstract things more. Regarding the update of nested attributes, I agree that there is not a good way to do it, hence this thread. =) @Michael Jones Maybe something like this could work

Re: [elm-discuss] Re: Post Examples of Painful Record Updates Here!

2017-03-06 Thread Michael Jones
Nothing special and I'm a beginner so I might be doing something stupid but I'm attempting to have some nested data in my model and this is the current state of one of my update functions which is fairly painful. update : Business.LocationList.Model.Msg -> Model -> ( Model, Cmd