Michael Martin

This probably affects (and hopefully resolves?) #31.

Oops, looks like a typo in the example... that `json` argument should probably be fed into the actual decoder. :) Try `let decodeColor = json => D.string(json) |> Relude.Result.flatMap(parseColor);` and...

Reopening, just to make sure I don't forget to go update those docs. :D

I admit I've only really used Js.Json directly for encoding. But this has come up enough that I'm definitely not opposed to adding useful utilities here. I'm not quite sure...

Just an update on this one: - I agree that symmetric encoding/decoding is not always what you want. In fact, in our application (which has a Reason frontend but a...

I haven't added it to the docs yet, but it's definitely possible without modifications: ```reason module Comment = { type t = { text: string, author: string, timestamp: Js.Date.t, likes:...

I'm definitely not opposed to this. I'm pretty sure Elm's decoders have a newtype wrapper like that, and I honestly don't remember why I chose to go the plain function...

Just to add to the findings... - The `[@ocaml.text]` solution works! Thank you! - I can't seem to use `{1 Heading}` style comments in reason syntax at all unless I...

With #2487 merged, this can probably be closed.

This can probably be closed now that Reason supports OCaml's monadic/applicative `let` syntax, yes?