PageComponentSchema.dataSource 在 list-view 之外仍无人消费:element:record_picker 丢 view,object-grid/form/kanban/calendar 等整条绑定不读(按 spec 写 dataSource 渲染出空)

[yinlianghui]

发现于 objectstack#5576 的实现过程(objectui PR,把 dataSource 接到 list-view)。#5576 的完成范围只到 list-view + resolveElementDataSource,本单是同一条绑定在其余 page component 上仍然无人消费,单独立单;实现要用 #5576 落地的公共 helper,故 Blocked-by: objectstack#5576。

事实(objectui origin/main + #5576 分支实测)

PageComponentSchema.dataSource(ElementDataSourceSchema)声明在每一个 page component 上 —— 它不是 list-view 专属键。但整仓只有两处读它:

packages/components/src/renderers/basic/record-picker.tsx:71   const ds = (schema?.dataSource ?? {}) as { object?; filter?; sort?; limit? }
packages/plugin-list/src/ListViewBlock.tsx                     (#5576 新增)

由此两个仍然存在的缺口:

1. element:record_picker 读了 4 个键、丢掉 view

record-picker.tsx:71-80 显式取 object / filter / sort / limit,没有 view。作者写 dataSource: { object: 'account', view: 'hot' } 得到的是未过滤的全量选择器,而不是 saved view 选出的行 —— 与 #5576 在 list-view 上修掉的是同一个「声明了但丢弃」形状,只是换了个 block,且症状更隐蔽(它不报错,只是答案更宽)。

2. 其余 object-bound public block 整条绑定都不读

object-grid / object-form / object-kanban / object-calendar / object-chart / object-metric / record:related_list 等都没有把 dataSource.object 映射到自己读的 objectName。一张页面上给 object-grid 按 spec 写 dataSource: { object, view } 而不写 objectName,渲染出来是空的(objectName 未设 → 不发查询)。

补充一条容易误读的:在 #5576 之前这些 block 写 dataSource 会直接坏掉(SchemaRenderer 把 schema 的 dataSource spread 成 prop,遮蔽了宿主注入的适配器 → dataSource.find is not a function)。#5576 已在 SchemaRenderer 侧把该键移出 prop spread,所以崩溃面已经消除;剩下的是本单的「读不到 = 静默空」。

建议范围

复用 #5576 落地的公共件,不要各 block 再写一遍:

• @object-ui/core:isElementDataSourceConfig / collectSavedViews / resolveSavedView / composeElementDataSource
• @object-ui/react:useElementDataSource(schema, dataSource?)(已含 saved view 抓取 + 「view 名解析不到就报错、不回退全量」的语义)

逐 block 接线 + 每个 block 两方向各钉一条(带/不带 dataSource),并沿用 #5576 定下的合成语义(filter 为 additional 走 and 合成;sort/limit 显式键覆盖 view;view 提供基线、组件自身显式键覆盖 view)。

为什么不并进 #5576

#5576 的验收线是 list-view 的两方向复现 + resolveElementDataSource 不再丢 view;把 7 个以上 block 的接线并进去会让那个 PR 的回归面无法逐块论证。分开做,每个 block 有自己的钉子。

[os-project-manager]

Triage (maintainer-authorized one-off pass, 2026-08-09 — registered on #6015): graded pm:blocked (state was missing — the card had routing repo:objectui but no pm-state label).

• Grade rationale: defect-class and well-evidenced (spec-declared dataSource silently unread on record_picker's view key and on every other object-bound block — the "declared but dropped" shape PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576 fixed for list-view). But the body itself scopes implementation to reusing PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576's helpers (useElementDataSource et al.) and names the serialization: Blocked-by: objectstack#5576 (open, pm:queue, target:v17). Blocked until that lands.
• Board note for the objectui seat: PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576 already carries target:v17; whether this follow-on card boards too is the objectui producer's call at unblock time (class ② arguable — spec-valid metadata renders empty), not made here.
• Dedup: PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576 is the anchor; element:record_picker.filter inputs-gap is separately tracked (objectui#3830). Clean.

---

Generated by Claude Code

[os-project-manager]

Unlock sweep (maintainer-requested, 2026-08-09): UNBLOCKED — pm:blocked → pm:queue. Blocker #5576 closed completed 2026-08-09T06:51Z — the shared helpers this card's implementation plan depends on (useElementDataSource, composeElementDataSource et al.) are on objectui main. The composition semantics recorded in the body (view as baseline, explicit keys override, filter composes via and, unresolvable view errors instead of falling back to full scope) are now the landed precedent to follow. Board question (class ② candidacy) remains the objectui producer's call at dispatch.

---

Generated by Claude Code

[yinlianghui]

🔒 认领(objectui 分片 PM,session_01GTRjn8xBqp75dk7kFupRVt 更正为 session_01GTRjn8xBqp75dk7kFupVRt,恢复批次 4;代码落 objectstack-ai/objectui)

• 分支(objectui 仓):claude/issue-6953-datasource-block-wiring
• 前置确认:Blocked-by PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576 已于 2026-08-09T06:51Z 关闭(PR fix(sharing)!: a rule with no criteria shares NOTHING, not every record (#3896) #3929 合入),useElementDataSource/composeElementDataSource 等公共件在 objectui main —— 解锁 sweep 已转回 pm:queue。
• 范围:record_picker 补 view 键 + 其余 object-bound block(object-grid/form/kanban/calendar/chart/metric/related_list)逐块接线,复用 PageComponentSchema.dataSource.view 是声明了但无人消费的绑定:objectui resolveElementDataSource 丢弃 view 键(除测试外零调用方),list-view 上照 spec 写 dataSource 反而运行时报错(17.0.0-rc.2) #5576 公共件,沿用其合成语义;每 block 两方向钉子。
• 文件面:packages/components/src/renderers/basic/record-picker.tsx + 各 packages/plugin-* 的 block 外壳(不动 core/react 的公共件本体;与在飞 fix(sharing,driver-sql): a rule authored in Setup actually applies — and switching it off actually withdraws access #3850+Explicit syntax for a legitimately optional filter condition (design only — no implementation until a real request) #3862 的 renderers/action/SchemaRenderer 面、objectui:ChartContainer 的 min-size 兜底被 {...props} 覆盖掉 —— ...props.style 那次合并是死代码 #7026 的 ChartContainerImpl.tsx 文件不相交)。

---

Generated by Claude Code