At ReactiveConf 2018, there was an amazing talk by Sean Grove on Reason and GraphQL titled ReactiveMeetups w/ Sean Grove | ReasonML GraphQL. The following is an excerpt from this talk that nicely summarizes the problems and solution for using JSON in Reason:
So I would argue that, in typed languages, like Reason, there are three really, really big problems when you want to interact with the real world. The first is all the boilerplate that it takes to get data into and out of your type system.
The second is, even if you can program your way out of the boilerplate, you are still worried about the accuracy, the safety of conversion.
And then finally, even if you if you get all of this and you're absolutely sure you've caught all the variation, someone can still change it from underneath you without you knowing.
How many times do we get a changelog whenever...
The second is, even if you can program your way out of the boilerplate, you are still worried about the accuracy, the safety of conversion.
And then finally, even if you if you get all of this and you're absolutely sure you've caught all the variation, someone can still change it from underneath you without you knowing.
How many times do we get a changelog whenever...