Schema definition and validation with support for decoding to bridge the gap between runtime types and static types.
Explore the docs »
Conformist allows you to define schemas to decode, validate and sanitize input data declaratively. It comes with runtime types for primitive OCaml types such as int, string, bool, float and Ptime.t, option and custom types. Re-use business rules in validators and run it on the client side with js_of_ocaml. Arbitrary meta data can be stored in schemas which is useful to build functionality on top of conformist.
Typical use cases are enforcing invariants of models or user input sanitization.
In essence, conformist helps you to keep your runtime types/contracts in sync with your static types.
opam install conformistIn your dune file:
(executable
(name app)
(libraries
...
conformist))
Let's look at an example.
type occupation =
| Mathematician
| Engineer
type user =
{ occupation : occupation
; email : string
; birthday : Ptime.t
; nr_of_siblings : int
; comment : string option
; favorite_shows : string list
; wants_premium : bool
}
let user
occupation
email
birthday
nr_of_siblings
comment
favorite_shows
wants_premium
=
{ occupation
; email
; birthday
; nr_of_siblings
; comment
; favorite_shows
; wants_premium
}
;;
let occupation_decoder = function
| [ "mathematician" ] -> Ok Mathematician
| [ "engineer" ] -> Ok Engineer
| _ -> Error "Unknown occupation provided"
;;
let occupation_encoder = function
| Mathematician -> [ "mathematician" ]
| Engineer -> [ "engineer" ]
;;
(* This is for example purpose only.
Please use emile (https://github.com/dinosaure/emile) instead *)
let validate_email value =
if String.index value '@' > 0 then None
else Some "This doesn't look like an email"
let user_schema =
Conformist.(
make
[ custom occupation_decoder occupation_encoder "occupation" ~meta:()
; string "email" ~validator: validate_email
; datetime "birthday"
; int ~default:0 "nr_of_siblings"
; optional (string "comment")
; list (string "favorite_shows")
; bool "wants_premium"
]
user)
;;
let input =
[ "occupation", [ "engineer" ]
; "email", [ "[email protected]" ]
; "birthday", [ "2020-12-01T00:00:00.00Z" ]
; "nr_of_siblings", [ "3" ]
; "comment", [ "hello" ]
; "favorite_shows", [ "Iron Man"; "Avengers" ]
; "wants_premium", [ "true" ]
]
;;
let user = Conformist.decode user_schema input
let validation_errors = Conformist.validate user_schema inputTry to delete/swap some lines of the list of fields, to change the constructor or the user type. The compiler forces you to keep these three things in sync.
Decoding doesn't validate the data, it just makes sure that the types are correct and translates strings to the correct static types.
Note that if decoding of a field fails, validation fails as well. Before a field is validated, it gets decoded.
Since we are shadowing the list [], dune warnings might fail compilation depending on the configuration. Suppress warning -40 can help.
The documentation for the latest released version can be found here.
Copyright (c) 2020 Oxidizing Systems
Distributed under the MIT License. See LICENSE for more information.
The implementation of this project was inspired by archi and re-web.