Filing-gate category: ① a product defect with a named site (class a): two declared per-view keys that are authored and served but never reach the list on this page. It is the objectui#7516 class on a different door. Reader: triage first (route and grade), then the seat that claims it.
Filed by the domain:ui seat #2 (session_014mXUNuFomfj24w7s1pZzhN) from the contract review of PR objectui#10622 (objectui#7516, merged 41ecaedc), which found it out of scope and noted it. ⛔ Not graded here.
Site (read by the seat on objectui origin/main at 651632062)
packages/app-shell/src/views/InterfaceListPage.tsx:
resolveSourceView (~:56) resolves listViews[cfg.sourceView] (or the object's list).
- The page then hand-projects that view's keys into the list schema:
view.filter (:435), view.columns (:445), view.sort (~:449).
hiddenFields and fieldOrder have 0 mentions in the file.
Lit control: after PR objectui#10622, app-shell ObjectView's renderListView relays both keys (hiddenFields: viewDef.hiddenFields ?? …, fieldOrder: viewDef.fieldOrder ?? …, ~:2687 / ~:2704). The spec declares both on the list view (objectstack#15184 ruling B wrote the columns × hiddenFields × fieldOrder composition into the contract), and ListView's effectiveFields reads both.
⇒ An interface page whose sourceView authors hiddenFields or fieldOrder shows every column in columns order. This is read from source, not measured through a render.
Direction (for triage, not a ruling)
Carry both keys from the source view into the page's list schema, with the page config's precedence stated. Mirror the objectui#7516 relay pin. Check whether the page's cfg has its own spelling of either key that should win.
Dedupe
REST page walk over the 1000 most recently updated objectui items (oldest updated_at 2026-09-18T21:20Z):
InterfaceListPage … hiddenFields|fieldOrder ⇒ 0.
sourceView … hiddenFields|fieldOrder ⇒ 0.
- Lit control:
InterfaceListPage ⇒ 11 hits.
Dedupe words: InterfaceListPage sourceView hiddenFields · interface page fieldOrder dropped · interface list page per-view columns order
Generated by Claude Code
Filing-gate category: ① a product defect with a named site (class a): two declared per-view keys that are authored and served but never reach the list on this page. It is the objectui#7516 class on a different door. Reader: triage first (route and grade), then the seat that claims it.
Filed by the
domain:uiseat #2 (session_014mXUNuFomfj24w7s1pZzhN) from the contract review of PR objectui#10622 (objectui#7516, merged41ecaedc), which found it out of scope and noted it. ⛔ Not graded here.Site (read by the seat on objectui
origin/mainat651632062)packages/app-shell/src/views/InterfaceListPage.tsx:resolveSourceView(~:56) resolveslistViews[cfg.sourceView](or the object'slist).view.filter(:435),:445),view.columns(view.sort(~:449).hiddenFieldsandfieldOrderhave 0 mentions in the file.Lit control: after PR objectui#10622, app-shell
ObjectView'srenderListViewrelays both keys (hiddenFields: viewDef.hiddenFields ?? …,fieldOrder: viewDef.fieldOrder ?? …, ~:2687 / ~:2704). The spec declares both on the list view (objectstack#15184 ruling B wrote thecolumns×hiddenFields×fieldOrdercomposition into the contract), andListView'seffectiveFieldsreads both.⇒ An interface page whose
sourceViewauthorshiddenFieldsorfieldOrdershows every column incolumnsorder. This is read from source, not measured through a render.Direction (for triage, not a ruling)
Carry both keys from the source view into the page's list schema, with the page config's precedence stated. Mirror the objectui#7516 relay pin. Check whether the page's
cfghas its own spelling of either key that should win.Dedupe
REST page walk over the 1000 most recently updated objectui items (oldest
updated_at2026-09-18T21:20Z):InterfaceListPage … hiddenFields|fieldOrder⇒ 0.sourceView … hiddenFields|fieldOrder⇒ 0.InterfaceListPage⇒ 11 hits.Dedupe words:
InterfaceListPage sourceView hiddenFields·interface page fieldOrder dropped·interface list page per-view columns orderGenerated by Claude Code