No node type, no schema-driven config verdict
The rule
Normative: this is the rule
- When a node's node type does not resolve there is no derived config schema to judge its
configagainst, so the schema-driven checks of R6 (required keys, type,enum, bounds,pattern, and the unknown-key warning) are not applied to that node, and produce neither error nor warning for it. - The unresolvable node type is reported by R9.
What it means
Without a resolved node type there is nothing to derive a config schema
from, so none of R6's schema-driven checks run for that node — not the
required-key check, not type or enum or bounds or pattern, and not even
the unknown-key warning a stray key would otherwise draw. The node is silent
on all of it, favourably or not: a key nobody declared draws no warning
either, for want of anything to compare it against.
That silence does not reach the config's own shape. A node whose type does
not resolve still has its config checked for being an object at all
(R6.a) — the skip is for the schema-driven checks alone.
Example
{"undeclared": "value"}Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · R6.j · changed in spec 1.0