FA-26289 / Filter interfaces / Member archive

No-element matching still has operands while empty and missing modes do not · case 04

No-element matching still has operands while empty and missing modes do not is violated by the widget projection.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

Collection-valued fields expose any/all/none element match modes distinct from empty-collection and missing-field predicates; switching to unary collection modes removes element operands. This example checks: No-element matching still has operands while empty and missing modes do not.

Why this case matters

Filter-widget state and serialization must preserve user constraints while the view changes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
contract fixture 0	`{"all-empty-warning": false, "element-editor": true, "empty-collection-evidence": false, "operator-key": "collection.empty", "quantifier-caption": "empty collection", "unary-collection-value": null}`	`{"all-empty-warning": false, "element-editor": false, "empty-collection-evidence": false, "operator-key": "collection.empty", "quantifier-caption": "empty collection", "unary-collection-value": null}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.