Upgrade path for Deprecated Boolean Codec about bs-json HOT 4 CLOSED

Mmm... good to know!

Thanks :)

from bs-json.

You can just use the bool encoder/decoder instead, can't you? The serialization format for that is, was and will continue to be js booleans.

The commit you link to was made to maintain backwards compatibility for those that haven't updated, and to not break semantic versioning. And because of how bsb works, that means compiler warnings for everyone until a new major version is pushed. I wanted to get some bigger changes into a new major release too, but might consider doing one just to get rid of the warnings. It would be much better if the warning issue was fixed in the bsb side though.

Closing this as answered, but let me know if you still have questions.

from bs-json.

Any plans for the next major version number?

from bs-json.

Big plans. Primarily a more expressive way to decode objects, which also would enable a Result-based API that I'm considering doing at the same time. Not sure whether it would be less painful to make it one big change, or to do it piecemeal.

Here's what decoding an object probably will look like:

Json.Decode.(
  obj (fun ~field -> {
    start     = field.required "start" point;
    end_      = field.required "end" point;
    thickness = field.optional "thickness" int
  })
)

from bs-json.