FA-25849 / Filter interfaces / Member archive

Unary constraints omit operand keys instead of leaking prior values · case 04

Unary constraints omit operand keys instead of leaking prior values is violated by the widget projection.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

The filter wire format represents scalar, set, range and unary constraints with distinct operand structures; omission differs from a null scalar operand. This example checks: Unary constraints omit operand keys instead of leaking prior values.

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	`{"field-path": {"path": ["x"]}, "operator-preserve": "not-in", "range-envelope": {"lower": null, "upper": null}, "scalar-envelope": {"value": null}, "set-envelope": {"values": []}, "unary-envelope": {"operator": "not-in", "value": null}}`	`{"field-path": {"path": ["x"]}, "operator-preserve": "not-in", "range-envelope": {"lower": null, "upper": null}, "scalar-envelope": {"value": null}, "set-envelope": {"values": []}, "unary-envelope": {"operator": "not-in"}}`	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.