ResolveException

The one failure type of Resolver.resolve: same inputs always produce the same tree or the same error — never a partial tree.

Each subclass carries a stable identity string that conformance fixtures assert against (message text is free-form context and never part of the contract):

• notABoolean, notAString, notAList, notAnObject — a present but wrong-typed value

• unknownDirective — an unregistered $-marker

• multipleMarkers — more than one $-key on a single object

• missingOption — a required option is absent

• malformedOption — an undeclared option key, or an option/pointer that fails to parse

• defsCycle — a reference cycle between defs entries

• maxDepthExceeded — runaway directive recursion

• layoutNotSingleNode — the layout root resolved to zero or many nodes

• childrenNotArray — a children value that is not a literal JSON array

• invalidTemplate — the view is not an object or has no layout

Inheritors