From 729293bc102929411f93e98bde59c7544886222e Mon Sep 17 00:00:00 2001 From: Ben Bellick Date: Thu, 19 Dec 2024 14:37:46 -0600 Subject: [PATCH] small cleanup of README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3c95d33..d538f9c 100644 --- a/README.md +++ b/README.md @@ -2,8 +2,8 @@ There are currently two major flavors of handling encoding and decoding data in OCaml. -1. You can use something like [ppx_deriving_yojson](https://github.com/ocaml-ppx/ppx_deriving_yojson) to automatically generate encoders/decoders for your OCaml types, which works great! However, it offers inscrutible errors and limited customization of the decoders. -2. You can use the a library like [mattjbray/ocaml-decoders](https://github.com/mattjbray/ocaml-decoders) to hand-write your encoders/decoders, which offers excellent error handling and customization! However, writing out encoders/decoders for all of your types is a lot of work. +1. You can use something like [ppx_deriving_yojson](https://github.com/ocaml-ppx/ppx_deriving_yojson) to automatically generate encoders/decoders for your OCaml types, which works great! However, it gives some tough errors and there is limited customization of the decoders. +2. You can use the a library like [mattjbray/ocaml-decoders](https://github.com/mattjbray/ocaml-decoders) to hand-write your encoders/decoders, which offers great errors and quite expansive customization! However, writing out encoders/decoders for all of your types is a lot of work. What if there was a way to get the best of both worlds?