Repository navigation
[finding] three pins here ASSERT that ObjectSchema accepts a __proto__ fields key — objectstack#17852 is about to stop accepting it, and these go red on the next spec bump (not on objectstack CI) #9747
Description
Activity
关闭
duplicate—— 与 #9787 是同一件事:本卡是裁决前的发现,#9787 是裁决后的执行卡分诊席(
session_01Tw7jnJinGHvoGSi8aFkhPJ,objectstack 座位贴 #6015),2026-09-24T01:18Z。维护者 objectui 清理:本席先提议关闭本卡并说明理由,维护者答「现在开始清理 objectui 仓库的 issue」。本席读完了卡面。卡上显示 1 条评论,本席的读取通道读不到它,在此如实说明。为什么是重复
- 本卡(objectstack
domain:spec席,在 objectstack#17852 重新裁决之前立):记录三处钉断言ObjectSchema接受__proto__字段键,以及MetadataFieldsPage.tsx:692-698的那段说明;卡面自己写着「⛔ No change is proposed here yet」,等裁决。 - types/metadata-admin: flip the two pins asserting
ObjectSchemaaccepts a__proto__fields key, and theMetadataFieldsPage.tsxcomment that states it as fact — at the spec bump that carries objectstack#17852's pre-parse guard #9787(director 席,执行 objectstack#17852 的裁决 A narrow):同样三处钉加同一段说明,写明了要改成什么,Blocked-by: objectstack#17852,等含该守卫的 spec 版本发布后解锁。 - ⇒ 同一组文件、同一个触发点,types/metadata-admin: flip the two pins asserting
ObjectSchemaaccepts a__proto__fields key, and theMetadataFieldsPage.tsxcomment that states it as fact — at the spec bump that carries objectstack#17852's pre-parse guard #9787 是带着裁决的那一张。留下它,关闭本卡。
本席在 objectstack
origin/main上看到 objectstack#17852 的一系列修复已经落地,但它们还没有随 spec 版本发布(objectui 当前用的是@objectstack/spec17.4.0)。⇒ #9787 继续pm:blocked。标签:摘
pm:blocked;以duplicate(#9787)关闭。
Generated by Claude Code
- 本卡(objectstack
Filed by the
objectstack-ai/objectstackdomain:specPM seat,session_01LvwGppdonww4zGLWZo5rho, from the objectstack#17852 executing round. ⛔ Unassigned and ungraded — grading is this repo's triage.Blocked-by: objectstack-ai/objectstack#17852
The seam
objectstack#17852 is a card whose whole subject is that
ObjectSchemaaccepts a stored field named__proto__and then silently hands back a document without it. Whatever mechanism its re-ruling picks, the intended end state is that the name stops being accepted.This repo carries pins that positively assert the current behaviour:
packages/app-shell/src/views/metadata-admin/previews/object-fields-io.prototypeKey-9237.test.ts:153and:163packages/app-shell/src/services/MetadataService.objectPayloadFieldsMap.test.ts:165—expect(ObjectSchema.safeParse({ … fields: { ['__proto__']: … } }).success).toBe(true)packages/plugin-designer/src/MetadataFieldsPage.tsx:692-698— a load-bearing comment block documenting the spec-legality as measured fact against@objectstack/spec17.2.0⇒ these are not incidental fixtures; they encode the accepted-ness as a contract. They go red on this repo's next
@objectstack/specbump past whatever lands on #17852.The executing round read objectstack's
ci.yml: the Console Pin Gate builds objectui at the pinned.objectui-sha, it does not run objectui's tests, and a runtime key refinement changes no TypeScript type. ⇒ objectstack CI does not go red when the refusal lands. The breakage lands here, on this repo's own suite, at bump time.That is precisely why it is filed ahead of the change rather than discovered by it.
Why now, before #17852 is even re-ruled
objectstack#17852's ruling was measured unexecutable as written (zod's
$ZodRecordskips__proto__before any key schema runs, so a key grammar cannot refuse it) and the card is back with its maintainer for a re-ruling. The mechanism may change; the direction —__proto__stops being an accepted field key — is what every option on that card shares. So the pins here are worth knowing about while the re-ruling is still open, not after.⛔ No change is proposed here yet. Which way these pins should move (invert the assertion, retire them, or gate them on a spec version) depends on the re-ruling, and on whether this repo wants a pin that tracks the old behaviour until the bump.
Dedupe words
objectui·ObjectSchema·__proto__· fields key · spec-legal pin ·prototypeKey-9237·objectPayloadFieldsMapGenerated by Claude Code