Hi Tim, For an in depth discussion on Json Decode you might want to refer to article on Medium about Json Decode API and Json Decode Pipeline API.
https://medium.com/@kkruups/elm-insights-c74047637206#.phhn8xvml I would love to get your feedback on the article. Kkruups On Wednesday, November 16, 2016 at 8:06:26 PM UTC+9, Tim Bezhashvyly wrote: > > Thanks! > > On Wednesday, November 16, 2016 at 12:04:21 PM UTC+1, Janis Voigtländer > wrote: >> >> "fieldName" := Json.list anotherDecoder becomes field "fieldName" >> (Json.list anotherDecoder) >> >> >> 2016-11-16 11:44 GMT+01:00 Tim Bezhashvyly <[email protected]>: >> >>> Sorry if I'm asking something obvious but with changes to Json.Decode in >>> 0.18.0 I'm not quite sure how to pass results of one decoder to another. >>> >>> So in 0.17.1 it was: >>> >>> decoder : Json.Decoder SomeType >>> decoder = >>> Json.object1 identity >>> ("feildName" := Json.list anotherDecoder) >>> >>> object1 becomes map, "feildName" := Json.list becomes field >>> "fieldName" Json.list. Just not sure about anotherDecoder. >>> >>> Thank you. >>> >>> -- >>> 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 [email protected]. >>> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
