markz

examples

Every example markz is held to that is kept as a file, in the one fence format fences.ts reads.

  • upstream/: the vendored suites, one file each, with the suite's own numbers and what checks them in each file's metadata; the sweeps curation keeps off the Conformance page are in upstream/stress/.

  • markz/: markz's own, one file per construct and one for the Not supported rows, numbered in one sequence (markz:17).

Folders

  • markz/

    markz's own examples: one file per construct, named by its id in syntax.md ({#id}), and not-supported.md with a ## for each Not supported row's warning code. The format is ../../harness/fences.ts's.

  • upstream/

    Vendored upstream examples, read-only inputs to the oracle harness, one file per suite in the fence format fences.ts reads. Each file's metadata names the suite's source at its pinned commit and what its examples are checked by: oracle (micromark), yaml, slug or math. Examples keep the suite's own numbers, as commonmark:42. The expected output in them is each suite's own; markz is compared with its oracle, not with it, and the oracle is checked against it where it has any. The files are generated, so the formatter leaves them alone, and examples.test.ts holds each to exactly what fences.ts writes.