FAILURE MAP
← Case archive

FA-25093 / Filter interfaces / Member archive

Only errors for the current submission appear on its filter summary · case 03

Only errors for the current submission appear on its filter summary is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

The applied-filter summary distinguishes settled, pending and failed draft updates, and uses the server-acknowledged filter revision for result badges. This example checks: Only errors for the current submission appear on its filter summary.

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 fixtureActualExpectedOutcome
contract fixture 0{"dirty-count": 2, "error-scope": true, "result-fresh": true, "result-label": "updating", "retry-payload": null, "revision-pending": true}{"dirty-count": 2, "error-scope": false, "result-fresh": true, "result-label": "updating", "retry-payload": null, "revision-pending": true}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.

Sign in to the archive ↗