isFieldComparisonSatisfied
isFieldComparisonSatisfied(
predicate,data):boolean
Whether a FieldComparisonPredicate is satisfied by data — a client-side port of the server’s
own evaluator, and the same one EbitexForm and ebitex’s own hosted form page use, so show/hide
decisions cannot drift between a renderer you write and the ones ebitex ships.
Comparison is string-based against the submitted value’s string form, matching the server exactly:
no numeric-coercion table for either implementation to disagree on. A submitted array (a Checkbox
answer) satisfies Equals when any element matches, and counts as empty only when it has zero
elements. A missing/null answer behaves as “no answer” for every operator — the same rule that
lets a hidden field’s controlling condition collapse coherently through further conditions, since a
respondent’s browser never submits an answer for content it never showed.
It is tested against the same set of cases as the server’s evaluator, so the two agree.
Parameters
Section titled “Parameters”predicate
Section titled “predicate”Returns
Section titled “Returns”boolean