FA-24913 / Filter interfaces / Member archive

Range validation compares numeric endpoints and accepts point ranges · case 03

Range validation compares numeric endpoints and accepts point ranges is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

A numeric range editor preserves open ends, treats zero as a bound, and rejects reversed finite endpoints before applying. This example checks: Range validation compares numeric endpoints and accepts point ranges.

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	`{"empty-constraint": false, "endpoint-order": false, "lower-handle": 2, "lower-open": 2, "upper-handle": 10, "upper-open": 10}`	`{"empty-constraint": false, "endpoint-order": true, "lower-handle": 2, "lower-open": 2, "upper-handle": 10, "upper-open": 10}`	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.