Contents specifies how user-defined contents need to be serializable and mergeable.
The user needs to provide:
t to be used as store contents.t (built using the Irmin.Type combinators).merge function, to handle conflicts between multiple versions of the same contents.Default implementations for idempotent string and JSON contents are provided.
Values.
module type S = sig ... endContents of type string, with the default 3-way merge strategy: assume that update operations are idempotent and conflict iff values are modified concurrently.
Json contents are associations from strings to json values stored as JSON encoded strings. If the same JSON key has been modified concurrently with different values then the merge function conflicts.
module Json_value : S with type t = jsonJson_value allows any kind of json value to be stored, not only objects.
module V1 : sig ... endmodule type STORE = sig ... endContents store.