All conformance tests

/conf/then/

• /conf/then/apply-each: Two invocations that both fail on the same node produce two results.
• /conf/then/apply-each-problem: One invocation whose function returns two problems produces two results.
• /conf/then/field: With field, the function sees the named property of the matched node.
• /conf/then/field-jsonpath: A field that is a JSONPath expression applies the function to every value it selects.
• /conf/then/field-key: With field: "@key" on a matched object, the function sees each of its property keys; the key that does not match the pattern is reported.
• /conf/then/field-missing: With field naming a property the node lacks, the function sees no value, so defined fails.
• /conf/then/field-path: A field that is a path of property names reaches a nested value.
• /conf/then/function-core: A rule naming a core function is valid.
• /conf/then/function-missing: An invocation without function is invalid.
• /conf/then/function-options: The max option reaches the length function.
• /conf/then/function-unknown: A rule naming a function that is neither core nor declared is invalid.
• /conf/then/invocation-form-valid: An invocation with function, field, and functionOptions of the right types is valid.
• /conf/then/options-not-object: An invocation whose functionOptions is a string is invalid.
• /conf/then/options-on-no-option-function: truthy with options is invalid, because it takes none.
• /conf/then/options-required-missing: length with empty options is invalid, because it needs min or max.
• /conf/then/options-unknown-value: casing with type: lower, which is not a case the function knows, is invalid.
• /conf/then/options-valid: Core functions with options that match their tables are valid.
• /conf/then/shape-empty-array: A rule with then: [] is valid.
• /conf/then/shape-string: A rule whose then is a string is invalid.
• /conf/then/shape-valid: then as a single invocation and as an array of them are both valid.