FA-25463 / Filter interfaces / Member archive

Explicit empty equality is valid while empty broad-match operands are not · case 03

Explicit empty equality is valid while empty broad-match operands are not is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Text filters distinguish exact, prefix and contains modes; literal punctuation remains literal, and trimming and case policy are explicit editor options. This example checks: Explicit empty equality is valid while empty broad-match operands are 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	`{"case-policy": "", "case-serialization": {"case_sensitive": true}, "empty-permitted": false, "literal-preview": "", "mode-caption": "is exactly", "trim-policy": ""}`	`{"case-policy": "", "case-serialization": {"case_sensitive": true}, "empty-permitted": true, "literal-preview": "", "mode-caption": "is exactly", "trim-policy": ""}`	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.