Re: [elm-discuss] Parsing JSON — one more victim

@Rex: I join this chant: nice trick this one on debugging — once more, thanks, Peter! (and, yes, this community os awesome!) @Peter: I've seem things that belong to the “public/common” such as a decentralized Twitter or Chicago transit timetable

Re: [elm-discuss] Parsing JSON — one more victim

On Tuesday, July 26, 2016 at 7:27:25 AM UTC-4, Eduardo Cuducos wrote: > > You could be very mean due to my typo. > This is the Elm Community, we don't do mean here :) I had a similar, infuriating JSON decoding bug due to a simple typo that took me hours to find ... argh! :) Peter, I didn't

Re: [elm-discuss] Parsing JSON — one more victim

Yay, deployed: https://github.com/cuducos/cunhajacaiu It's a tiny project that I use to test my Elm skills and, surely, to learn Elm. Nothing very complex, Elm is updating the stopwatch, and loading the news — loading both initial data from different JSON API (but once loaded, no interaction is

Re: [elm-discuss] Parsing JSON — one more victim

To paraphrase Satchmo, "If lots more of us helped each other, we’d solve lots more problems. And then this world would be better." I'm glad I could help. ;) On Tue, Jul 26, 2016 at 2:27 PM, Eduardo Cuducos wrote: > Peter, thank you so much. > > You could be very mean due to

Re: [elm-discuss] Parsing JSON — one more victim

OK, So, first, you had a typo in the decoder. it says "chidren" instead of "children" This is why it is better to first debug the decoder with fake but valid data and then move to retrieve the data from a live source. You do this by just prettifying the json and pasting it into a triple quote

Re: [elm-discuss] Parsing JSON — one more victim

The links you tried to post are broken. Have you tried creating a small sample JSON to test your decoders on? On Tue, Jul 26, 2016 at 11:17 AM, Eduardo Cuducos wrote: > Hi all, > > I'm tryind to parse Reddit JSON > <#m_1784857688894315202_m_-844639499985301489_> but I