Loading…
Loading…
The compiler never throws away the document over one bad line. It is forgiving by design: it always produces the best diagram it can and reports what it could not use, so a typo never leaves you with a blank canvas.
line N: … diagnostic.unknown color "purpel" (did you mean: purple?).secuence) or directive (layout: sideways) still draws
as a node, with a warning that says what it was read as. Put the line in
quotes when a node is what you mean.{ is never closed is an error on the
line that opened it.The example below has three problems: an unknown colour, an unknown shape, and an edge with no target. The diagram still renders, and each problem reports underneath.
diagnostic · line 1: unknown attribute "chartreuse"
diagnostic · line 2: unknown attribute "octahedron"
diagnostic · line 3: edge needs both ends
An unknown word in an attribute list is dropped on its own; the words around it are still used. Here the colour survives even though the shape word is unknown.
diagnostic · line 1: unknown attribute "octahedron"
Diagnostics come in two severities. A warning (amber) means something was ignored but the diagram is intact: an unknown word, an unknown colour. An error (red) means a whole line could not be parsed. Both surface in the code panel, keyed to the line, and neither stops the diagram from rendering.