[elm-discuss] Re: Http 401 Interceptor? My 3rd Elm Project - authentication

HttpError has BadResponse Int String which you can use to detect non-200 results to http requests. The way to do it in elm is to write a function that wraps the creation of login enabled http requests and translates 401 errors into a suitable message (which is why Task.perform has two function

[elm-discuss] Re: no user not a github project

I discovered this recently when trying out elm-server-side-renderer . The elm compiler is parsing the repository url in elm-package.json and using what would be the user name and repository fields for these. Apparently, what you have is what happens when the repository url doesn't point to

Re: [elm-discuss] Re: Any tricks for debugging?

Ahh, I needs it! Just spent last night trawling through chrome dev console looking at single line formatted debug.log, finally found the bug after an hour but it took me back to js days... Because all your business logic is explicitly reflected in your model, being able to step and look at

[elm-discuss] ANN: elm-light 0.4.0 - AST driven Elm features in Light Table

Hi ! After quite a few weeks of working evenings and nights I'm finally ready to announce the 0.4.0 release of the Elm language plugin for Light Table . I guess the big thing is that I've created a parser (using a parser generator, PEG.js) to give me the

Re: [elm-discuss] Re: Any tricks for debugging?

Well elm-conf 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

Re: [elm-discuss] Re: Any tricks for debugging?

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 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

[elm-discuss] Re: Any tricks for debugging?

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 which

Re: [elm-discuss] Upgrading 0.16 `Effects.task <| Task.succeed` to 0.17

One of the following two pages/sections of the FAQ should solve that for you: http://faq.elm-community.org/17-tasks.html http://faq.elm-community.org/17.html#how-do-i-generate-a-new-message-as-a-command ​ 2016-09-15 20:30 GMT+02:00 Rex van der Spuy : > Hi Everyone! > >

[elm-discuss] Re: Upgrading 0.16 `Effects.task <| Task.succeed` to 0.17

I'm not from 0.16, but here is how I send a message to myself, I have this in a Helpers module: ```elm cmd_from_msg : msg -> Cmd msg cmd_from_msg msg = Task.perform (\_ -> Debug.crash "This cannot fail") identity (Task.succeed msg) ``` Which would turn your code into this if I understand

Re: [elm-discuss] Elm app crashing in Chrome/Firefox

Great, many thanks, Peter : ) On Thu, Sep 15, 2016 at 11:11 AM Peter Damoc wrote: > The url-parser example shows this: > > https://github.com/evancz/url-parser/blob/master/examples/App.elm#L104 > > > > On Thu, Sep 15, 2016 at 4:30 PM, Eduardo Cuducos >

Re: [elm-discuss] Elm app crashing in Chrome/Firefox

The url-parser example shows this: https://github.com/evancz/url-parser/blob/master/examples/App.elm#L104 On Thu, Sep 15, 2016 at 4:30 PM, Eduardo Cuducos wrote: > Hum… that sounds interesting. > I'm not refactoring it right now, but gonna try this next time I go back > to

Re: [elm-discuss] Elm app crashing in Chrome/Firefox

Hum… that sounds interesting. I'm not refactoring it right now, but gonna try this next time I go back to that code. Do you have any snippet as reference? Many thanks, On Thu, Sep 15, 2016 at 8:40 AM Peter Damoc wrote: > As a suggestion: > Don't modify the URL directly. Create

Re: [elm-discuss] Elm app crashing in Chrome/Firefox

As a suggestion: Don't modify the URL directly. Create some kind of helper function that would allow you to navigate using a higher level of structure. I have the concept of Pages in my app (i.e. locations where certain parts of the functionality gets accomplished). When I want to navigate, I

Re: [elm-discuss] Elm app crashing in Chrome/Firefox

Many thanks for you reply, Peter. Indeed changing that line to Cmd.none fix the issue. The reason why I (naïvely) added that Navigation.modifyUrl "" was to clean up a “invalid” URL. For example: if location is #/document/42, this is a valid entry point; but is the location happens to be

[elm-discuss] Any tricks for debugging?

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

[elm-discuss] Re: Permission denied: Elm package install

Same as David Legard for me, stopped working in a dropbox folder, moved to non syncing and it worked. Haven't seen the issue anymore. On Wednesday, September 14, 2016 at 6:03:35 PM UTC+3, kiran kumar BS wrote: > > Hello Team, > > I am trying to setup a small ELM project but failed due to some

Re: [elm-discuss] Type Alias With Arguments

Thanks! -- 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.