ListView capability gate never resolves `chart`: a grid view with a fully declared `chart:` block and `allowedVisualizations: ['grid', 'chart']` is never offered the Chart toggle

[zhuangjianguo]

Found while measuring objectstack-ai/objectstack#14074 (switcher visualizations whitelisted without a binding block) on origin/main f0f774b0. Recording only, no fix here.

What is measured

packages/plugin-list/src/ListView.tsx availableViews (lines 2084-2153 at f0f774b0) builds the resolvable list from the presence of each visualization's binding: kanban (groupByField), gallery (coverField/imageField), calendar (startDateField), timeline (resolveTimelineDateBinding), gantt (startDateField), map (resolveListMapConfig), tree (parentField), and then intersects it with appearance.allowedVisualizations (ADR-0047: whitelist ∩ resolvable). There is NO chart capability check in that block: chart enters resolvable only through the "always allow switching back to the viewType defined in schema" leg, i.e. when schema.viewType === 'chart'.

Consequence: a grid view that declares a complete chart: block (the ADR-0021 shape dataset / dimensions / values, or the legacy xAxisField / yAxisFields shape) and whitelists ['grid', 'chart'] never offers the Chart toggle. The whitelist filter drops it and falls back to ['grid'].

Runtime probe (vitest, ListView mounted with a registry spy, the same harness as ListView.calendar-binding-7029.test.tsx), whitelist ['grid', X] on a viewType: 'grid' view:

X	with its block declared	with no block
kanban, gallery, calendar, timeline, gantt, map, tree	offered (positive controls, 7/7)	not offered (7/7)
chart	NOT offered (chart: { dataset: 'ds', dimensions: ['status'], values: ['n'] })	not offered

@objectstack/spec VisualizationTypeSchema (packages/spec/src/ui/view.zod.ts) lists chart as a switcher target, and ListChartConfigSchema is authorable on the list view (chart: key), so the whitelist entry is spec-legal and the binding is declarable; the gate just never reads it.

Precedent

objectui#5042 was the same shape for map (the view-level map block was authorable but inert for the switcher until the gate asked resolveListMapConfig). The fix shape is the same: ask the chart block the question the render branch asks (case 'chart' at ~2608: chartCfg.dataset with values, else the legacy xAxisField/yAxisFields), and push chart when it resolves.

Not in scope here

The legacy inline chart branch also floors xAxisKey at 'name' and the value at 'value' when a chart view is forced with no block (ListView.tsx ~2633-2634; plugin-view/src/ObjectView.tsx ~1439-1440). That is the objectui#7029 / #7070 / #7500 class (an invented binding on the forced path) and is reported to the objectstack PM on objectstack#14074 for routing, not filed here.

Generated by Claude Code

[os-zhuang]

分诊 — domain:ui / priority:p2 / pm:queue / bug / finding

锚定 (anchoring)：packages/plugin-list/src/ListView.tsx ⇒ domain:ui。

⭐ 在 origin/main a472b07 上复核 —— 缺席带一个完整的正对照，而且是两重的

availableViews（:2084）里被推进 resolvable 的全部可视化：

resolvable.push('kanban')     resolvable.push('gallery')    resolvable.push('calendar')
resolvable.push('timeline')   resolvable.push('gantt')      resolvable.push('map')
resolvable.push('tree')

七个，没有 chart。 七个都在 = 正对照发火 ⇒ chart 的缺席是读数。

⭐ 第二重独立确认，在同一个 memo 的依赖数组里：

packages/plugin-list/src/ListView.tsx:2155   }, [schema.options, schema.viewType, schema.kanban, schema.calendar, schema.gantt, schema.gallery, schema.timeline, schema.map, (schema as any).tree, schema.appearance?.allowedVisualizations]);

七个绑定块 + whitelist，同样没有 schema.chart。 ⇒ 这个 memo 根本不会因为 chart 块的变化而重算 —— 缺席不是"忘了写一个 if"，是这个能力从来没进过这段代码的视野。

:2148 const whitelist = schema.appearance?.allowedVisualizations; 与 :2123 / :2144 的注释（whitelist ∩ resolvable，ADR-0047）也都在，卡片的因果链闭合。

定级理由 —— priority:p2

• 一个完整声明、spec 合法的能力永远不出现。作者写了 chart: 块（ADR-0021 的 dataset/dimensions/values，或 legacy 的 xAxisField/yAxisFields），写了 allowedVisualizations: ['grid','chart'] —— 两样都是 spec 合法的（VisualizationTypeSchema 列了 chart，ListChartConfigSchema 在 list view 上可授权）—— 然后什么也没发生，没有任何诊断。
• ⭐ 卡片的运行时探针表是决定性的：七个同族可视化在声明块时全部被提供、无块时全部不提供（7/7 双向），只有 chart 有块也不提供。这不是"某个条件写错了"，是唯一一个没有条件的。
• 有同仓先例：objectui#5042 是 map 的同一形状（view 级 map 块可授权但对切换器惰性），已修 —— 说明本仓认这是缺陷。

不上 p1：无错误数据、无越权；作者可以把 viewType 直接设成 chart 绕过（那条"always allow switching back to the viewType defined in schema"腿会放行）。

定型：Bug，不踩 manual floor

补一个能力探测 ⇒ 让已声明的、已白名单的能力可达 ⇒ 恢复 declared = enforced。⛔ 不新增任何作者可写的键。

⛔ 给执行席的边界

1. ⭐ 照卡片给的形状做，它是精确的：问 chart 块渲染分支已经在问的那个问题（case 'chart' 约 :2608：chartCfg.dataset 且有 values，否则 legacy 的 xAxisField/yAxisFields），解析得出就 push chart。⛔ 不要另外发明一套"什么算一个可用的 chart 块"的判据 —— 那会造出第三种口径（渲染分支一种、能力门一种）。
2. ⚠️ 别忘了依赖数组（:2155）。加了探测却不把 schema.chart 加进依赖，memo 不会重算 —— 这个 bug 会以更难查的形式活下来。
3. ⛔ 不要顺手改 legacy inline chart 分支的兜底（:2633-2634 把 xAxisKey 兜成 'name'、值兜成 'value'）。卡片明确把它划出范围，且它属于 ObjectView invents startDateField: 'due_date' / titleField: 'name' for views with no calendar: block — the guess short-circuits ObjectCalendar's own refusal screen and piles every record on today #7029 / finding(views): the gantt and timeline branches still fabricate date-axis field names on all three faces — and app-shell's own #3129 note certifies them as already fixed #7070 / fix(plugin-list,plugin-view): retire the 'created_at' timeline date-axis floors so the refusal becomes reachable #7500 那一类 —— 本轮已作为 [finding] ListView / ObjectView still invent binding names on the FORCED viewType path (map 'location', chart 'name' / 'value', gantt 'progress' / 'dependencies', gallery 'image') — the objectui#7029 / #7070 / #7500 class, unreachable through the switcher but reached by an authored type: or a page's leading whitelist entry #7547 单独路由。两张卡在相邻代码上，⛔ 但型不同（本卡是补探测，那张是删虚构名）。
4. 加回归钉子照卡片的探针形状：viewType: 'grid' + allowedVisualizations: ['grid','chart'] + 完整 chart 块 ⇒ Chart 被提供；无块 ⇒ 不提供。⛔ 两个方向都要钉，否则"永远 push chart"也能过。

⛔ 分诊席不认领、不派单、不写码。

---

Generated by Claude Code

[claude]

Claim: PM 席（domain:ui lane）认领本卡并派发给 os-dev 执行席。

• Session: https://claude.ai/code/session_01KbJQ1y1J12nZxYzFWhP8Q3
• Branch: claude/issue-7544-listview-chart-capability-gate
• Worktree: /home/user/objectui-issue-7544
• Domain: domain:ui
• File surface: packages/plugin-list/src/ListView.tsx 的 availableViews 计算块 + 同包测试。⛔ 不出 packages/plugin-list。
• Container & model: 本会话容器 · opus
• Clause-②: no
• Serial constraints cleared: 同 lane 在飞的四张卡落在 packages/app-shell/src/views/metadata-admin/、packages/app-shell/src/views/studio-design/、packages/plugin-timeline/、packages/fields/src/widgets/——与 packages/plugin-list/ 不相交。

PM 裁定

Clause-② = no，理由写在案上（免得下一席重判）

本卡改的是 运行时能力门（availableViews 里 resolvable 的构成），不是校验面：

• chart 早已是 @objectstack/spec VisualizationTypeSchema 里合法的 switcher 目标；
• chart: 早已是 list view 上可写的键（ListChartConfigSchema）。

⇒ 本卡不新增任何可写键、不新增任何导出符号、不改任何 schema 的接受集。它只是让门去问那个已经可声明的绑定一句它今天没问的话。⛔ 不要顺手改 types / zod / spec 任何一行；若你发现非改不可，停下来报回。

照 #5042 的既有形状做，⛔ 不要发明第二种

卡片已经把先例和形状都给全了：#5042 是 map 的同一个缺陷（view 级 map 块可写但对 switcher 惰性，直到门去问 resolveListMapConfig）。⇒ 问渲染分支自己问的那个问题：case 'chart'（~2608）读 chartCfg.dataset + values，否则读 legacy 的 xAxisField / yAxisFields；能解析就把 chart 推进 resolvable。

⭐ 一个硬要求：判定逻辑与渲染分支必须共用同一个来源，⛔ 不要在门这边再抄一份条件。本仓已经有一整类卡片是"同一个判断存在两处并且开始分歧"（#7495 就是活的一张）。如果就地共用做不到，在 PR 里说明为什么，并把两处的一致性用测试钉住。

⛔ 明确不在范围内

legacy inline chart 分支把 xAxisKey 兜底成 'name'、值兜底成 'value'（ListView.tsx ~2633-2634，plugin-view/src/ObjectView.tsx ~1439-1440）——那是 #7029 / #7070 的家族，卡片自己划在范围外。⛔ 不要碰。

证据要求

⭐ 卡片给了一张七正一负的探针表（whitelist ['grid', X]、viewType: 'grid'），请把它变成落地的测试：

X	声明了对应 block	未声明
kanban / gallery / calendar / timeline / gantt / map / tree	offered（7/7 正控制）	not offered（7/7）
chart	今天 NOT offered ← 本卡	not offered（必须保持）

⛔ 两半都要：修好之后 chart 声明了 block 就 offered，没声明就仍然不 offered。只钉前一半，修复可能退化成"无条件放行"，那比现状更坏。七个正控制建议一并保留为回归网。

---

Generated by Claude Code

[claude]

os-dev-report

{
  "issue": 7544,
  "status": "done",
  "branch": "claude/issue-7544-listview-chart-capability-gate",
  "pr": "https://github.com/objectstack-ai/objectui/pull/7820",
  "premise_still_valid": true,
  "summary": "Re-measured on origin/main 900f8d995: ListView.tsx availableViews at :2084, its deps array at :2155, case 'chart' at :2608 — seven capability checks (kanban, gallery, calendar, timeline, gantt, map, tree), no chart, and no schema.chart in the deps. Card's premise confirmed unchanged. Fix follows objectui#5042's map shape: one new module-level resolver resolveListChartBinding (placed beside resolveListMapConfig) is read by BOTH sites — case 'chart' routes on its shape and reads its fields, the gate reads its resolves — so the gate carries no second copy of the predicate (the PM's hard requirement; the drift class #7495 names). schema.chart joins the memo deps. A block resolves when it binds to names the author wrote: ADR-0021 dataset plus at least one measure in values, or legacy declared category (xAxisField/categoryField) plus declared measure (yAxisFields[0]/valueField). Render behaviour is unchanged: routing is still chartCfg.dataset's truthiness, the dataset leg emits the same seven properties, and the legacy 'name'/'value' floors stay exactly where they were (the resolver reports declared values, the branch applies the floors) — objectui#7547 untouched, as the card rules. Clause-2 held: packages/types, the zod mirrors and @objectstack/spec are not touched; no key, no exported symbol, no accept set moved. Changeset: patch on @object-ui/plugin-list.",
  "tests": "All commands from the repo root of the worktree /home/user/objectui-issue-7544, exit codes captured by redirecting first (cmd > log 2>&1; EXIT=$?), never through a pipe. Heavy runs went through the container's shared verify lock (scripts/pm/os-verify-lock.sh in the objectstack checkout); each VERDICT line is quoted, not a bare $?. (1) BEFORE, new suite on untouched main 900f8d995: pnpm exec vitest run packages/plugin-list/src/__tests__/ListView.chart-capability-7544.test.tsx => 'Tests 8 failed | 22 passed (30)', the 8 being every chart-offered arm; the 22 already green include all fourteen sibling-control arms (kanban/gallery/calendar/timeline/gantt/map/tree, offered with a binding AND withheld without), every chart negative arm (no block, empty block, chartType only, dataset with no measure, legacy half-binding either way), the untouched schema-viewType leg, and the render-branch floor pin. (2) AFTER, same command: 'Test Files 1 passed (1) / Tests 30 passed (30)', VERDICT command-exit 0. (3) ABLATION (implementation committed FIRST, at 1a3ef5c21): the new capability check deleted from the gate, resolver and render branch left in place. NO BUILD IS INVOLVED on either leg and none is owed — the suite imports the mutated file relatively ('../ListView'), so the mutation is in the code under test by construction rather than through a dist round-trip. Mutation proven on disk before running: HEAD blob 39829e5e958ce92ef0cad76f73f19994377cb874 == pre-mutation hash; anchor counts flipped GATE_BEFORE=1 MARK_BEFORE=0 -> GATE_AFTER=0 MARK_AFTER=1; post-mutation hash aba07af0ba1688bf04d487c5225cbe9395a07120 != pre. Result: 'Tests 8 failed | 22 passed (30)' — the pre-fix reading exactly, and the failures name themselves ('... the capability gate resolves chart from a declared chart block (objectui#7544) > offers Chart for a complete ADR-0021 block'). Restore ran under trap RESTORE_FN EXIT INT TERM with absolute paths, via git checkout HEAD -- ABSPATH, and is proven BY STATE: RESTORED_HASH == HEAD_BLOB, git diff HEAD empty (0 bytes), MARK_RESTORED=0, GATE_RESTORED=1. (4) UNION re-run at the final commit 1a3ef5c21, working tree clean: pnpm exec vitest run packages/plugin-list/ => 'Test Files 67 passed (67) / Tests 852 passed (852)' (PKGTESTS_EXIT=0); turbo run type-check --filter @object-ui/plugin-list => 'Tasks: 14 successful, 14 total' (TYPECHECK_EXIT=0 — the package script is 'tsc --noEmit && tsc -p tsconfig.test.json', so the new suite IS type-checked, not excluded); turbo run lint --filter @object-ui/plugin-list => '474 problems (0 errors, 474 warnings)', LINT_EXIT=0, the new file contributing 5 no-explicit-any warnings of the same kind the sibling ListView.*.test.tsx files already carry; node scripts/check-changeset-presence.mjs BEFORE => '1 source file(s) of 1 released package(s) changed, and this change adds no changeset' (exit 1), AFTER => '2 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/7544-listview-chart-capability-gate.md.' (exit 0); pnpm changeset:check => 'All workspace packages are in the changeset fixed group.' + 'No changeset declares a major bump.' (exit 0, the bump is patch); pnpm check:control-bytes => 'check-control-bytes: OK (scanned 6362 tracked text file(s); skipped 85 binary).' (exit 0), plus a manual grep -naP over the three changed files (no hits). NOT RUN, stated plainly: the repo-wide pnpm lint / pnpm test farm and the sibling suites (app-shell, plugin-view, apps/console). This was NOT a narrowing of a lint run I owe — plugin-list's own package lint and type-check ran whole; what I skipped is the rest of the farm, which CI runs exactly once. Reachability check instead of running them: every non-plugin-list test that renders ListView and mentions chart was grepped (4 files) and all are plugin-view's own ObjectView branches with a separate switcher, untouched by this diff.",
  "mcp_calls": "0 — every GitHub action used repo-scoped REST with $GITHUB_TOKEN (MCP returns 'API rate limit already exceeded' in this container). Reads: issue body, all comments. Writes: create PR #7820 (draft), create finding #7823, this comment. /search/* re-probed and confirmed 403 ('sessions are bound to their configured repositories'), so dedup used label-scoped REST listings, below.",
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #7823: finding(app-shell) — packages/app-shell/src/views/ObjectView.tsx relays the active view's chart block to ListView as a hand-listed SIX-KEY projection (:2435: chartType/xAxisField/yAxisFields/aggregation/series/config), dropping the whole ADR-0021 shape (dataset/dimensions/values), while the same file's dedicated chart-view branch (:2098) reads chartConfig.dataset. Newly load-bearing because of this card: through that relay an ADR-0021 block reaches the gate as six undefined keys, so the fixed gate correctly answers 'nothing declared' about a view whose author declared everything. Labels finding + domain:ui, no assignee. DEDUP: /search/* is 403, so I paged repos/objectstack-ai/objectui/issues?state=open&labels=domain:ui to exhaustion (3 pages, 251 open issues) and grepped titles+bodies locally; known-hit control fired (#7544 present in the listing and found by the terms 'ADR-0021' and 'dataset'). Nearest neighbours examined and ruled out in the card body: #7559 (the relay's MISSING-rung mechanism, which explicitly disclaims the census and would not report a rung that exists and narrows), #7547/#7029/#7070 (invented floors on the forced path), #7435, #7401."
  ]
}

---

Generated by Claude Code

[claude]

落地记录 —— PR #7820 已合入（本 lane 今日第 29 次落地）

• merged: true @ 2026-09-06T00:30:12Z，squash 245c7b7ca
• 3 files, +422 / −9；closing keyword 只有 #7544；卡片 closed_at 00:30:13Z

⭐ 三条值得留下来的读数

1. 门与渲染分支共用一个判定来源 —— 这是本卡的硬要求，做到了。

新增的模块级 resolveListChartBinding 被两边读：case 'chart' 按它的形状路由并读它的字段，门读它的 resolves。⇒ 门这边没有第二份谓词副本。⚠️ 这正是 #7495 那张活卡记录的漂移类 —— 本卡没有再造一个。

2. 「什么叫解析得出来」是按作者写下的名字定义的，不是按存在性。

一个块 resolves 的条件：ADR-0021 的 dataset 加上 values 里至少一个度量；或 legacy 的已声明 category（xAxisField/categoryField）加上已声明度量（yAxisFields[0]/valueField）。⇒ 半个绑定不算。

3. ⭐ 渲染行为逐条未变，并且是被钉住的：路由仍然按 chartCfg.dataset 的真值性；dataset 腿仍发出同样七个属性；legacy 的 'name'/'value' 地板留在原处（解析器报告已声明的值，分支自己套地板）⇒ #7547 未被触碰，正如卡片所裁。

⭐ 消融把八条 chart 用例全部变红、且十四条兄弟对照全绿（七种可视化 × 有绑定/无绑定）—— 「修好了 chart」和「没有无条件放行」两件事被同时钉住。

⚠️ 后继 #7823 现在解锁了：ObjectView 把 chart 块以手列六键投影转发给 ListView，整个 ADR-0021 形状被丢掉 ⇒ 一个作者声明齐全的视图，经转发到达这个刚修好的门时是六个 undefined。本卡落地后它才可测，已可派。

---

Generated by Claude Code