I’m using bs-json and it’s cool, but…, it is not pipe-first and so kinda doesn’t fit perfectly the idiomatic ReScript. And it encourages completely isolated encoding and decoding which is quite error-prone if you talk with JSONs to yourself (for example in a [micro-]service project). Kudos to @glennsl, I just trying to take another look to the problem.
How is it? Feedback is much welcomed. Not all features are implemented yet but the basis is ready. I’ll extend this if I see the concept makes sense.
Jzon is a decoding and encoding library whereas bs-decode supports only the former, as I understand.
I did not found this library when I was looking for something similar. Now I see, yes, they are quite similar. One notable difference though is where the lib boundary is drawn. JsonCodec offers to define codecs that take tuples in and give tuples out. And Jzon requires the functions to construct/destruct the destination type, so that, codecs take objects in and give objects out.
No, unfortunately, found no spare time to arrange a solid experiment. Yet.