Constraint Matrix

This matrix provides a compact overview of which constraints are applicable to which node types.

It is intended as a quick reference for rule authors. For precise semantics, edge cases, and value-type requirements, always refer to the individual constraint documentation.

Legend

— The constraint is defined and meaningful for this node type.
— The constraint must not be used with this node type.

Important

“Supported” only indicates that a constraint may be used with a given type. It does not imply that all value forms of the constraint are valid. For example, some constraints accept different value types depending on context.

Constraint Applicability Matrix

Type → / Constraint ↓	Integer	Boolean	Float	Text	Date	Time	DateTime	Bytes	TimeDelta	RegEx	Value	Value Lists [1]	Sections [2]
chars not_chars
equals
in
key
matches
minimum maximum
multiple
starts ends contains
version minimum_version maximum_version

Notes

Version constraints apply to node-rules definitions, not to configuration values themselves. They therefore appear as supported for all node types.
Constraints affecting entry counts (e.g. minimum, equals, multiple) apply to lists and sections only when those nodes represent collections.
Constraints not listed here (such as case_sensitive or is_optional) are flags, not value constraints, and are therefore intentionally excluded from this matrix.