When you’re writing JSON decoders, it’s helpful to understand what’s going on.
When you’re up in the clouds with your JSON workflow doing all sorts of fancy and advanced stuff, it’s great!
But what about when you don’t need all the fancy stuff?
(Or you’re just getting started?)
It’s a hassle to write decoders, objects, and encoders for every single field by hand.
It feels like tedious boilerplate.
But really, you don’t have to do it all by hand.
Please meet JSON to Elm.