# Experimental JSON decoding API

**URL:** <https://discourse.elm-lang.org/t/experimental-json-decoding-api/2121>\
**Category:** Request Feedback\
**Created:** [October 4, 2018, 4:21am UTC](https://discourse.elm-lang.org/t/experimental-json-decoding-api/2121 "2018-10-04T04:21:50Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![brasilikum](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brasilikum/32/524_2.png) [@brasilikum](https://discourse.elm-lang.org/u/brasilikum)\
**Post date:** [October 10, 2018, 5:19am UTC](https://discourse.elm-lang.org/t/experimental-json-decoding-api/2121/28 "2018-10-10T05:19:29Z")

</div>

As feedback from beginners was explicitly requested:  
I understood the examplecode right away and had an “aaaahh” moment because:

This style of writing decoders resembles “normal” elm code much more than the current syntax. It was intuitively obvious that I now had access to all previously decoded values, just like I do while pattern matching.

I have written a small elm app for internal tooling so far but did not understand the current syntax enough (even after three tries) to be able to decode a type where one value depends on two others.

I don’t really mind the additional lines of code as I think it fits with the rest of elm which seems to favor being explicit over being concise. Also I am sure elmjutsu and the other awesome plugins would be able to autocomplete a reasonable amount of code.

---

_[View the full topic](https://discourse.elm-lang.org/t/experimental-json-decoding-api/2121)._
