Error Handling in Definitions

Errors that arise from header definitions and references.

Definitions are resolved after the entire header has been read, and references are checked again as data is validated. Two errors are specific to definitions:

Condition	Error code	Cause
Reference to an undefined schema or type	schema-not-defined	$name is used but no $name is defined anywhere in the header
Reference to an undefined variable	variable-not-defined	@name is used but no @name is defined anywhere in the header

Error codes are stable; messages and positions may vary between implementations. Branch on the code, not the message.

Undefined schema reference

A $ reference must name a schema or type defined in the header. An undefined name fails with schema-not-defined:

~ $schema: { name: string, home: $address }
---
~ John, { Main St, NYC }    # ✗ schema-not-defined — $address is never defined

Undefined variable reference

A @ reference must name a variable defined in the header. An undefined name fails with variable-not-defined:

~ $schema: { name: string, isActive: bool }
---
~ John, @active             # ✗ variable-not-defined — @active is never defined

Reference order

Because definitions resolve only after the whole header is read, order within the header is not significant — a reference MAY appear before the definition it targets. The following resolves even though $address is defined after the schema that uses it:

~ $schema: { name: string, home: $address }
~ $address: { street, city }
---
~ John, { Main St, NYC }    # ✓

For readability you SHOULD still define a reference before you use it; doing so reads top to bottom and makes the dependency obvious.

See Also

• Definitions · Schema References · Variables

• Error Model — the full error catalogue