JSON codec backed by Formata.JSON.Backend.
Decoding
- Any JSON value may be the root (objects, arrays, and scalars).
- Object keys stay strings.
- Duplicate object keys are rejected with a
:parse/:duplicate_keyerror (RFC 8259 leaves their meaning undefined; Formata does not pick one). - Numbers become integers or floats; numbers outside the float range are a syntax error reported by Formata.JSON.Backend.
- Syntax errors carry the byte offset reported by Formata.JSON.Backend and the line/column derived from it.
Options (both decode-only, independent, and false by default, so a plain
decode/2 is strict RFC 8259):
:comments- accept//line comments (to the end of the line) and/* ... */block comments (non-nesting, must be closed) wherever JSON allows whitespace. Comment-like text inside strings is string content. Positions in errors refer to the original input.:trailing_commas- accept a single comma after the last element of a non-empty array or object ([1, 2,],{"a": 1,}). Empty slots such as[1,,2],[,],{,}, or a doubled trailing comma are always rejected.
This is the "JSONC" mode; there is no separate JSONC codec. For a .jsonc
file use Formata.decode(input, :json, comments: true, trailing_commas: true)
(or only the extensions the file format allows). Comments are not preserved.
# comments and JSON5 syntax are not accepted; use :json5 for JSON5.
Unknown options and non-boolean values are rejected with :unsupported /
:invalid_option errors.
For incremental parsing of a single document arriving in chunks, see
Formata.Codec.JSON.Stream.
Encoding
The JSON domain is nil, booleans, integers, finite floats, UTF-8 strings,
lists, and maps with string keys. Atom keys, Date/DateTime values,
:infinity/:nan, tuples, and other terms are rejected; convert them
explicitly with Formata.Transform.
Options:
:pretty- pretty-print the output (defaultfalse).