Edge checks
- SHEET
- C3
- REV
- flowfig 0.8.4
- SOURCE
- src/guide.ts
- DATE
- 2026-10-05
This page is the output of npx flowfig docs verify. Your agent reads the same text.
Read this topic when the render prints a verify finding, or to check figures in CI.
If a box or an edge has a source or a via, the render checks each one against the code. The render reads the code from the
folder where it runs, so run it from the repo root. --no-verify skips this part. A verify finding does not stop the render.
Fix each finding:
missing-file: thesourcefile does not exist. Fix the path. The path is relative to the repo root.missing-symbol: the file has no such symbol or heading. Fix the name. A method usesOwner.name.edge-not-found: the code does not make that call. Remove the edge, or point itssourceat the function that makes the call.- An
unsureedge is allowed. If a function with a typed receiver makes the call, point the edgesourceat that function. - A
not checkededge has no code to check. Give it asourceor aviaif one exists.
Do not invent an edge to make the verify pass.
The count line has this form:
out.svg: 4 of 4 boxes defined; edges: 5 found, 0 not found, 1 unsure, 0 not checkedCopy the count line into the reply as printed.
For CI, npx flowfig verify <svg>... runs the same check on SVG files. --root <folder> sets the repo root. --json prints
JSON. --strict makes warnings errors.