Well elm-conf <http://www.elm-conf.us/> is happening right now, so we'll 
get more info very soon.

On Thursday, 15 September 2016 21:50:42 UTC+2, John Orford wrote:
>
> any ballpark guesses on when 0.18 will happen? before the end of the year 
> perhaps?
>
> On Thu, 15 Sep 2016 at 21:37 Zinggi <schrot...@gmail.com <javascript:>> 
> wrote:
>
>> You could wait some time on the 0.18 release which will most likely bring 
>> back the time traveling debugger, with object introspection.
>> This is much more comfortable than Debug.log.
>>
>> For now, you could use this library 
>> <http://package.elm-lang.org/packages/jinjor/elm-time-travel/latest> which 
>> also works quite nicely. (except if you have many messages per second, e.g. 
>> for game/animation things)
>>
>> Debug.log covers all the the other cases. However, if I wanted to print 
>> all messages, I'd do it like this:
>>
>> update msg model =
>>     case Debug.log "Msg" msg of
>>         Foo -> ...
>>
>>
>> On Thursday, 15 September 2016 12:24:46 UTC+2, Rupert Smith wrote:
>>>
>>> I am finding it useful to know which Msgs are being triggered through my 
>>> update functions, so have been putting in code like this:
>>>
>>> log =
>>>     Debug.log "myModule"
>>>
>>> ...
>>>
>>>         Add ->
>>>             let d = log "add" in
>>>                ...
>>>
>>> Now I have decided it would be easier to just print all Msgs rather than 
>>> add this to specific ones:
>>>
>>> debug : a -> a
>>> debug a =
>>>     Debug.log "myModule" a
>>>
>>>
>>> update : Msg -> Model -> ( Model, Cmd Msg )
>>> update action model =
>>>     update' (debug action) model
>>> -- OR even     update' (debug action) (debug model)
>>>
>>> update' : Msg -> Model -> ( Model, Cmd Msg )
>>>
>>> And am considering pulling up the 'debug' function into its own module, 
>>> so I can easily globally turn on/off debug tracing by switching it between 
>>> the identity function or the logging function.
>>>
>>> Just wondering if anyone has any helpfull debugging tricks they like to 
>>> use with Elm?
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Elm Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elm-discuss...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to