chore: release

CHANGES.md

@@ -1,3 +1,11 @@
+## 0.3.0 (2019-06-24)
+
+* Add `uncons` primitive (#7, @mattjbray)
+* Add `Decoders_sexplib` (#7, @mattjbray)
+* Add `Decoders_cbor` (#9, @mattjbray)
+* Add `Decoders_bencode` (#14, @c-cube)
+* Remove `containers` dependency (#16, @c-cube)
+
 ## 0.2.0 (2019-06-24)
 
 * Add `field_opt` decoder (#5, @actionshrimp)

LICENSE

@@ -0,0 +1 @@
+ISC

Makefile

@@ -1,4 +1,4 @@
-ALL_TARGETS=decoders.install decoders-cbor.install decoders-ezjsonm.install decoders-sexplib.install decoders-yojson.install decoders-cbor.install decoders-bencode.install
+ALL_TARGETS=decoders.install decoders-bencode.install decoders-cbor.install decoders-ezjsonm.install decoders-sexplib.install decoders-yojson.install
 
 .PHONY: build
 build:

README.md

@@ -281,6 +281,6 @@ After updating CHANGES.md:
 ```
 npm version <newversion>
 git push --tags
-dune-release -p decoders,decoders-ezjsonm,decoders-yojson
+dune-release -p decoders,decoders-bencode,decoders-cbor,decoders-ezjsonm,decoders-sexplib,decoders-yojson
 npm publish
 ```

decoders-bencode.opam

@@ -2,6 +2,19 @@ opam-version: "2.0"
 maintainer: "Matt Bray <[email protected]>"
 authors: ["Simon Cruanes"]
 synopsis: "Bencode interface for decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-bencode"
 bug-reports: "https://github.com/mattjbray/ocaml-decoders/issues"

decoders-cbor.opam

@@ -2,6 +2,19 @@ opam-version: "2.0"
 maintainer: "Matt Bray <[email protected]>"
 authors: ["Matt Bray <[email protected]>"]
 synopsis: "CBOR interface for decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-cbor"
 bug-reports: "https://github.com/mattjbray/ocaml-decoders/issues"

decoders-ezjsonm.opam

@@ -3,6 +3,19 @@ maintainer: "Matt Bray <[email protected]>"
 authors: ["Matt Bray <[email protected]>"]
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 synopsis: "Interface to ezjsonm for decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-ezjsonm"
 bug-reports: "https://github.com/mattjbray/ocaml-decoders/issues"
 license: "ISC"

decoders-ocyaml.opam

@@ -1,6 +1,19 @@
 opam-version: "2.0"
 maintainer: "Matt Bray <[email protected]>"
 synopsis: "YAML interface for ocaml-decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 authors: ["Matt Bray <[email protected]>"]
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-ocyaml"

decoders-sexplib.opam

@@ -2,6 +2,19 @@ opam-version: "2.0"
 maintainer: "Matt Bray <[email protected]>"
 authors: ["Matt Bray <[email protected]>"]
 synopsis: "Sexplib interface for decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-sexplib"
 bug-reports: "https://github.com/mattjbray/ocaml-decoders/issues"

decoders-yojson.opam

@@ -2,6 +2,19 @@ opam-version: "2.0"
 maintainer: "Matt Bray <[email protected]>"
 authors: ["Matt Bray <[email protected]>"]
 synopsis: "Interface to yojson for decoders"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 homepage: "https://github.com/mattjbray/ocaml-decoders"
 doc: "https://mattjbray.github.io/ocaml-decoders/decoders-yojson"
 bug-reports: "https://github.com/mattjbray/ocaml-decoders/issues"

decoders.opam

@@ -1,5 +1,18 @@
 opam-version: "2.0"
 synopsis: "Elm-inspired decoders for Ocaml"
+description: """
+A combinator library for "decoding" JSON-like values into your own Ocaml types, inspired by Elm's `Json.Decode` and `Json.Encode`.
+
+> Eh?
+
+An Ocaml program having a JSON (or YAML) data source usually goes something like this:
+
+1. Get your data from somewhere. Now you have a `string`.
+2. *Parse* the `string` as JSON (or YAML). Now you have a `Yojson.Basic.json`, or maybe an `Ezjsonm.value`, or perhaps a `Ocyaml.yaml`.
+3. *Decode* the JSON value to an Ocaml type that's actually useful for your program's domain.
+
+This library helps with step 3.
+"""
 maintainer: "Matt Bray <[email protected]>"
 authors: ["Matt Bray <[email protected]>"]
 homepage: "https://github.com/mattjbray/ocaml-decoders"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bs-decoders",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "",
   "main": "index.js",
   "directories": {