Module Yaml

value is the subset of a Yaml document that is compatible with JSON. This type is the same as Ezjsonm.value, and so most simple uses of Yaml can be interchanged with JSON.

yaml is the representation of a Yaml document that preserves alias information and other Yaml-specific metadata that cannot be represented in JSON. It is not recommended to convert untrusted Yaml with aliases into JSON due to the risk of denial-of-service via a Billion Laughs attack.

scalar is the description of a Yaml scalar.

Scalar values are represented as strings. A scalar can optionally have an anchor and a tag. The flow style of the scalar is defined by the style field. If plain_implicit is true, the tag is optional for the plain style. If quoted_implicit is true, the tag is optional for any non-plain style.

sequence is the description of a Yaml sequence.

Sequences are similar to JSON arrays. A Yaml sequence can have an s_anchor and an s_tag. If s_implicit is true, the s_tag is optional.

mapping is the description of a Yaml mapping.

Mappings are similar to JSON objects. A Yaml object can have an m_anchor and an m_tag. If m_implicit is true, the m_tag is optional. A key in a Yaml mapping can be an arbitrary Yaml node.

YAML provides three flow scalar styles: double-quoted, single-quoted and plain (unquoted). Each provides a different trade-off between readability and expressive power. The Yaml spec section 7.3 has more details.

Version of the YAML spec of a document. Refer to the Yaml specification for details of the differences between versions.

Document encoding. The recommended format is Utf8.

Mappings and sequences can be rendered in two different ways:

• Flow styles can be thought of as the natural extension of JSON to cover folding long content lines for readability, tagging nodes to control construction of native data structures, and using anchors and aliases to reuse constructed object instances.
• Block styles employ indentation rather than indicators to denote structure. This results in a more human readable (though less compact) notation.

This library uses the standard result type for returning errors rather than raising exceptions.

of_string s parses s into a JSON value representation, discarding any Yaml-specific information such as anchors or tags.

of_string_exn s acts as of_string, but raises Invalid_argument if there is an error.

to_string v converts the JSON value to a Yaml string representation. The encoding, scalar_style and layout_style control the various output parameters. The current implementation uses a non-resizable internal string buffer of 256KB, which can be increased via len.

to_string_exn v acts as to_string, but raises Invalid_argument in if there is an error.

pp ppf s will output the Yaml value s to the formatter ppf.

equal v1 v2 is true iff v1 and v2 are equal.

yaml_of_string s parses s into a Yaml yaml representation, preserving Yaml-specific information such as anchors.

yaml_to_string v converts the Yaml value to a string representation. The encoding, scalar_style and layout_style control the various output parameters. The current implementation uses a non-resizable internal string buffer of 256KB, which can be increased via len.

to_json yaml will convert the Yaml document into a simpler JSON representation, discarding any anchors or tags from the original. Returns an error if any aliases are used within the body of the Yaml input.

of_json j converts the JSON representation into a Yaml representation.

Low-level event streaming interface for parsing and emitting YAML files.