ocaml-jsonptr/test/ at main · gazagnaire.org/ocaml-jsonptr · Tangled

gazagnaire.org / ocaml-jsonptr

0

JSON Pointer token syntax (RFC 6901)

0

ocaml-jsonptr / test /

at main 4 files

Thomas Gazagnaire jsonptr: new nox-jsonptr package homes the RFC 6901 token syntax 6w ago

jsonptr: new nox-jsonptr package homes the RFC 6901 token syntax dupfind's biggest remaining cluster: pointer_encode_token, pointer_decode_token, pointer_decode_index and pointer_tokens were byte-identical between the json and yaml cursors. The pointer string syntax is value-type independent, so it moves to its own package (shared-standard rule: one RFC, two consumers) with RFC 6901 section 5 vectors, escape-ordering cases, and fuzz roundtrips; both cursors keep only their typed traversal and alias the syntax functions.

1 month ago

jsonptr: new nox-jsonptr package homes the RFC 6901 token syntax dupfind's biggest remaining cluster: pointer_encode_token, pointer_decode_token, pointer_decode_index and pointer_tokens were byte-identical between the json and yaml cursors. The pointer string syntax is value-type independent, so it moves to its own package (shared-standard rule: one RFC, two consumers) with RFC 6901 section 5 vectors, escape-ordering cases, and fuzz roundtrips; both cursors keep only their typed traversal and alias the syntax functions.

1 month ago

test_jsonptr.ml

jsonptr: new nox-jsonptr package homes the RFC 6901 token syntax dupfind's biggest remaining cluster: pointer_encode_token, pointer_decode_token, pointer_decode_index and pointer_tokens were byte-identical between the json and yaml cursors. The pointer string syntax is value-type independent, so it moves to its own package (shared-standard rule: one RFC, two consumers) with RFC 6901 section 5 vectors, escape-ordering cases, and fuzz roundtrips; both cursors keep only their typed traversal and alias the syntax functions.

1 month ago

test_jsonptr.mli

jsonptr: new nox-jsonptr package homes the RFC 6901 token syntax dupfind's biggest remaining cluster: pointer_encode_token, pointer_decode_token, pointer_decode_index and pointer_tokens were byte-identical between the json and yaml cursors. The pointer string syntax is value-type independent, so it moves to its own package (shared-standard rule: one RFC, two consumers) with RFC 6901 section 5 vectors, escape-ordering cases, and fuzz roundtrips; both cursors keep only their typed traversal and alias the syntax functions.

1 month ago