@inixiative/json-rules 3.9.0 → 3.11.0

package/README.md

@@ -628,6 +628,21 @@ declares: on Json, `contains` / `startsWith` / `endsWith` become `string_contain
 becomes one `equals` per value; on a scalar list, `contains` becomes `has` and emptiness
 `isEmpty`; `caseInsensitive` adds `mode: 'insensitive'` on text only.
 
+### A value the row doesn't carry
+
+By default `check()` reads an absent path as null, as a column is on the compiled rails.
+`check(rule, row, { absent: 'unknown' })` reads it as unknown instead: `null === null`, and
+`undefined` is not null. Every operator fails on an unknown field or compared `path`, `equals
+null` and `in [null]` included, except the ones that hold on a missing value (`isEmpty`,
+`notExists` and the negations), which keep their meaning. Use it when the row is a partial stand-in
+for real rows (a pseudo record a grant is checked against), so a rule passes only on what the row
+pins. `check()` only; the compilers read real columns.
+
+`validateRule(rule, { positive: true })` refuses every shape that can hold on a missing value —
+`if`/`then`/`else`, array and aggregate rules, the negations, `isEmpty` and `notExists` — so a rule
+checked that way passes only on what the row carries. A rule that means "no value" says `equals
+null`.
+
 ## Engine Globals
 
 `engineGlobals` holds process-wide defaults. Keys are dotted paths into one state object.