Repository navigation
[console] List sort: filterableFields doubles as the sort whitelist, and a header click discards the view's multi-level default with no way back #4243
Description
Two related gaps in the Console list view's sort experience, found while shipping a downstream app on @objectstack/*@17.0.0-rc.6. Both are capability requests, not defects — the platform behaves as currently designed.
1. filterableFields doubles as the sort-field whitelist; there is no way to open sorting without also opening filtering
Observed: a list view declares a two-level default sort (e.g. plan_start_date then name). Neither field appears in the Sort panel's field dropdown, and the sort rows render with blank field names. The dropdown's contents turn out to be exactly filterableFields minus relation-typed fields (lookup / master_detail / user / owner — consistent with the panel's own footnote about columns pointing at other records).
So the same array feeds both the Filter builder and the Sort builder. A field that should be sortable but not offered as a filter condition cannot be expressed: the only workaround is to add it to filterableFields, which also makes it appear in the filter condition builder.
Also note the asymmetry: a view can declare sort on a field the sort panel refuses to list. The declared default sort works on load, but the user cannot reproduce or modify it through the UI.
Request: either a dedicated sortableFields (spec has no such key today), or have the sort panel fall back to all non-relation fields rather than reusing filterableFields.
2. Clicking a column header replaces the entire multi-level sort, with no way back to the view's default
Observed: a view ships a two-level default sort. One click on any column header replaces the whole sort array with that single column. The view's declared sort acts only as an initial value — after that first click it is unreachable for the rest of the session; there is no "reset to default sort" affordance.
Combined with #1 this was worse: because the fields were not in filterableFields, the user could not even rebuild the original two-level sort by hand. Adding the fields to filterableFields restores the ability to rebuild it manually, but "restore the view's default" still requires a page reload.
Request: a way to restore the view-declared default sort (a reset control in the sort panel, or preserving the declared sort as a fallback tier under the ad-hoc header sort).
Environment
@objectstack/*@17.0.0-rc.6, Console list view. Verified against a clean database with no view overlay rows (sys_view_definition / sys_metadata type=view both empty), server restarted by port before capturing — i.e. the source-declared view is what rendered.
Downstream context
Reported from a private app repo, so screenshots are not linkable here. Happy to build a public minimal reproduction on a showcase app if that helps — just say the word.
Activity
os-zhuang commentedon Aug 11, 2026
Triage:
needs-user-decision.sortableFieldskey (contract change in objectstackpackages/spec; the key has zero hits across objectui @f812de6, counter-probe:filterableFieldsgreps fine) vs a console-side fallback to all non-relation fields. Part 2 (restore view-declared default sort after a header click) is console UX shape. Which direction part 1 takes decides whether an objectstack spec sub-card exists at all, so the ruling comes first.origin/main@f812de6:packages/plugin-list/src/ListView.tsx:1876-1883applies thefilterableFieldswhitelist to the field set, andpackages/plugin-view/src/SortUI.tsx:166builds the sort dropdown from that same filteredschema.fields— the "one array feeds both builders" claim holds.formulafields the server refuses) — different defect, different fix site; cross-repo search for a spec-sidesortableFieldscard: zero hits. No duplicate.本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
os-zhuang commentedon Aug 11, 2026
Maintainer ruling recorded 2026-08-11 (PM session, executing the maintainer's direct instruction in chat — verbatim: 「接受你的全部建议，请更新 issue 的状态和标签」, accepting the four-lens decision-inbox review in full).
Ruling: the narrow fix. (1) The Sort panel's field list falls back to all non-relation fields instead of reusing
filterableFields— ⛔ no newsortableFieldsspec key (a new vocabulary entry with no measured pull, against startup-focus). (2) Add a "reset to view default sort" affordance so a header click no longer makes the declared multi-level sort unreachable for the session.Scheduling: normal queue, NOT v17.
State:
needs-user-decision→pm:queue(objectui whole-repo seat).Generated by Claude Code
yinlianghui commentedon Aug 11, 2026
CLAIM — session
session_017Qqyix2QcnpUC9XeYVDzx3(objectui whole-repo PM seat),dispatching now. Branch:claude/issue-4243-sort-fallback-reset. Worktree-first.按 2026-08-11 已记录的维护者裁决执行(窄修,两半):(1) Sort 面板字段列表回退到全部非关系字段,⛔ 不新增
sortableFieldsspec 键;(2) 新增"恢复视图默认排序"控件。派单附加一条测量令:#3950(formula 字段被 server 拒排)是相邻卡——若 formula 类型确属 server 不可排,回退集合应把它一并排除并在 PR 正文说明(裁决的 ⛔ 在新词汇键上,不在合理的可排性排除上),但不修 #3950 的表头路径本身。Surface:
packages/plugin-list/src/ListView.tsx(白名单应用点 ~1876)+packages/plugin-view/src/SortUI.tsx(下拉源 ~166)+ 测试;当前无在飞持有者(#4267 已落,#4040 排除 plugin-list)。Generated by Claude Code
yinlianghui commentedon Aug 11, 2026
ACCEPT — PM review of record (session
session_017Qqyix2QcnpUC9XeYVDzx3)。PR #4299 按维护者裁决(窄修、⛔ 无新 spec 键)落地,验收要点:
UNMATERIALIZED_SORT_TYPES只含formula(chore(deps): Bump streamdown from 2.5.0 to 2.6.0 #6994 起硬 400),而 objectstack 自己的一致性测试明文警告"扩到 COMPUTED_VALUE_TYPES 会弄坏两个能用的类型"(summary/autonumber 有实体列)。渲染器的排除集与 server 逐一镜像、理由记在定义处。Grid/list columns offer a sort header onformulafields, which the server refuses as of framework#6994 #3950 的表头面按令未动。parseSortConfig(初始 useState 与视图切换已用的那一个 resolver),按 (field, order) 比较而非随机 id;与 handleHeaderSort 同级同通道(host 持久化 reset 与持久化表头点击同路)。无声明排序时隐藏的裁量合理(该控件的契约是"放回声明的",无声明即无物可回;清空已有删行方式,不发明第二个语义),且双分支 pin 防了"控件根本不存在所以 null 检查恒绿"的假阳性。#4294 定级采纳(bug 入队):提示文案教用户"加 formula 字段来排序"——恰是 server 唯一拒排的类型,与 objectstack 同场景提示语义相反。真实的反向指导,须修。
流程注记:revert-before-commit 的事故本日第二起(#4278 同型)。两名 dev 均自救成功且如实披露;commit-then-revert 已写入后续所有派单,另立文档卡把它进 AGENTS.md 的验证手册。
Flipping ready + auto-merge。
Generated by Claude Code
fix(list): sort picker falls back to all sortable fields, and gains a…
fix(i18n,list): the sort panel's relational hint points at a stored d…
docs(agents): require commit-then-revert for reverse verification (ob…