FA-37793 / Table interactions / Member archive

Table export projection: all versus view scope · case 03

The table all versus view scope result violates the stipulated table export projection contract.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Exports distinguish all source rows from current view rows and selected view rows; preserve view/schema order, omit forbidden columns, optionally include hidden columns, distinguish raw/display values with fallback, and disambiguate duplicate human labels in encounter order.

Why this case matters

An offline table UI model isolates table export projection, including adversarial row/column relationships.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
filtered view display	`{"columns": ["z", "b"], "labels": ["Value", "Value (2)"], "records": [["one", 2], [3, 4], [5, 6]], "row_ids": ["a", "b", "c"], "scope": "view"}`	`{"columns": ["z", "b"], "labels": ["Value", "Value (2)"], "records": [[3, 4], ["one", 2]], "row_ids": ["b", "a"], "scope": "view"}`	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.