Rasmus Klett

I think the definition of `optional` is very problematic. There are three distinct use cases where I would want to produce an `option`: 1. Return None if the field doesn't...

@glennsl Would you be open to a pull request switching `optional` to be strict, and adding a `decodeOrNone` implementing the current behaviour? This would be a slightly breaking change, I...

@ncthbrt You're right, that's probably a better strategy. @glennsl In my opinion the default `optional` decoder should match the JSON concept of a value which might be present. In some...

Warning: untested code ahead, I hope you get the point of it. Also I might be mixing Reason and OCaml syntax, sorry. The most often used I think would be...

> nullToNone already exists, it's called nullable (edit: actually nullable returns Js.null('a), so you'd have to then convert it to an option, but basically the same thing). There's also nullAs...

@glennsl Well, I don't agree with a lot of your response. I guess I have different ideas for how a library like this should look. I'm glad you like the...

After some discussion on Discord, I think the claim > ReasonML strings are encoded as UTF-8 and not compatible with JavaScript’s UTF-16 strings Is wrong. It also goes against the...

I've rewritten the core to use React Hooks, while keeping the old Component API, and adding .Jsx2 wrappers. In my opinion, this is really nice to use with Hooks instead...

Who do I need to contact to get a response? @cnguy @grabbou @knowbody?

Ah, that's really too bad. @grabbou can you confirm this repository is dead, and that you will not take a look at my changes?