Diagram types

ferrigura renders all 33 diagram types of Mermaid 12.2.0. Each type has a page here that describes how its text is parsed, how it is laid out and drawn, which settings it reads, and where it differs from Mermaid. The table below is the index: every type with the keywords that start it, its page, the layout engine that places its parts, and how far it is checked against the reference (0014).

A diagram type is a module inside the crates, not a crate of its own (ARCHITECTURE.md). Flowchart, class, state, ER and requirement share the unified renderer, and swimlanes, agentflow, use case, mindmap and block build on it; the other types have a renderer of their own. The layout engines are those of 0012. What porting taught across several types is in LEARNINGS.md.

Coverage

Reading the coverage

Each column is one of the checks of 0015, run against the reference. Specs counts the tests ported from Mermaid's own spec files for the type, passing over all, with the ignored ones named: an ignored spec carries #[ignore = "port: <reason>"], for example because it tests what ferrigura leaves out on purpose (0005). Differential parse is the number of inputs, the fixtures, the probes, the string literals of Mermaid's specs, the diagrams of its documentation and the cases of the harness, whose canonical models agree with the reference's, or which both sides reject; an input that differs only through a named exception is counted as agreeing, and the run fails on any other difference (0014). Layout data compares getData() field by field for the types on the unified renderer that have such a run. Geometry is the number of fixtures and probes, drawn by both sides in Chromium, whose boxes, positions, edge points and texts agree within 0.05 px, out of those both sides draw; "not compared" are the ones a rule of the harness leaves out, each with its reason: look: handDrawn, scripts that no bundled face covers, and inputs on which the reference itself fails. A dash means the type has no run of that kind, because it does not use the unified renderer; the layout engines have corpora of their own (LEARNINGS.md). For flowchart, the geometry run also checks that the graph given to ELK equals the reference's in all 298 fixtures. The cells of Specs, Differential parse, Layout data and Geometry are rewritten by pnpm -C tools/port port:status, which counts the specs with cargo test and reads the summaries of the last differential and geometry runs; a cell whose summary the checkout lacks keeps what it says. CI runs all the checks on every change.