FA-25937 / Filter interfaces / Member archive
Descending count order does not merge unknown with exact zero · case 02
Descending count order does not merge unknown with exact zero is violated by the widget projection.
Case contract
Facet ordering uses pinned then selected priority, descending known counts, and stable server order for ties; unknown counts sort behind known counts. This example checks: Descending count order does not merge unknown with exact zero.
Why this case matters
Filter-widget state and serialization must preserve user constraints while the view changes.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| contract fixture 0 | {"descending-count": ["c", "b", "a"], "pin-priority": ["b", "a", "c"], "pin-visible-only": [], "selection-priority": ["a", "b", "c"], "stable-count-ties": ["b", "a", "c"], "unknown-last": ["b", "a", "c"]} | {"descending-count": ["b", "a", "c"], "pin-priority": ["b", "a", "c"], "pin-visible-only": [], "selection-priority": ["a", "b", "c"], "stable-count-ties": ["b", "a", "c"], "unknown-last": ["b", "a", "c"]} | 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 ↗