Repository navigation
docs(vscode-extension): the Export to React page documents a clipboard the command never writes, and an example missing the side-effect import #7977
Description
content/docs/utilities/vscode-extension.mdx — the published page for the
extension, and the homepage its manifest points at — describes the
ObjectUI: Export to React command in two ways the command does not behave. Found
while measuring what that command promises about the JSX transform for
objectui#7862; neither is in that card's file surface, so both are filed.
1. It says the output goes to the clipboard. It does not.
The page's Usage list reads:
- React component code is copied to clipboard
exportToReact() in packages/vscode-extension/src/extension.ts does no such thing.
It calls vscode.workspace.openTextDocument with the generated content and
language: 'typescriptreact', shows it, and then shows the message
React component generated! Save it to a .tsx file. Nothing in the package writes to
the clipboard: the identifier clipboard does not occur in src/ at all. A reader
following the documented steps pastes whatever was on their clipboard already.
2. Its Output Example omits the side-effect import objectui#7837 established
The page's Output Example imports only SchemaRenderer from @object-ui/react. The
command's actual preamble also carries:
// Importing the package registers every default renderer as a side effect —
// there is no separate registration call.
import '@object-ui/components';That line is load-bearing. objectui#7837 measured it: @object-ui/components
declares sideEffects: true, its barrel runs import './renderers', and its built
dist/index.js carries 114 module-scope register( call sites. Without that import
no renderer is registered, so a user who copies the documented example rather than
running the command gets a SchemaRenderer with nothing to render.
Note on what is NOT wrong here
The example also shows no import React from 'react', which as of objectui#7862 is
correct and matches what the command now emits. That half of the page was already
right and should be left alone.
Why nothing catches either one
The command's output lives inside a template literal, so this package's
tsc --noEmit sees one string; the doc gates that read content/docs check fence
languages, snippet types and links, none of which can compare a documented example
against the generator that is supposed to produce it. Same mechanism as
objectui#7837 and objectui#7862, a third surface over.
Filed unassigned; a maintainer should decide whether the fix is to correct the prose
or to bind the page's fence to the template's product the way objectui#7862's pin
now binds the compile.
Generated by Claude Code
Activity
os-zhuang commentedon Sep 6, 2026
分诊：
domain:devx/bug+documentation/pm:queue/priority:p3落点核实（
origin/main）——两条都成立，且第一条带活控制① 剪贴板那句在，而剪贴板不在：
范围内活控制（否则 0 不可信）：同一目录里
⇒ 目录可搜、模式有效 ⇒ 「
clipboard在src/里一次都不出现」是读数，且:205/:213正是卡片描述的真实行为（开一个新文档并提示保存为.tsx）。⇒ 一个照着文档步骤操作的读者，粘贴的是他剪贴板里原本的东西。 卡片零错。
② 副作用 import 的缺席：卡片说页面的 Output Example 只 import 了⚠️ 本席未逐字比对该 mdx 的 Output Example 与模板产物，⛔ 不把这一半当作已复现继承下去。但它的载重论证是可核的（objectui#7837 测得：
SchemaRenderer，而命令实际产出的前言还带import '@object-ui/components';。@object-ui/components声明sideEffects: true，其 barrel 跑import './renderers'，构建出的dist/index.js带 114 个模块级register(调用点）⇒ 没有那一行，一个渲染器都不会注册，读者拿到一个没有东西可渲染的SchemaRenderer。⭐ 卡片主动指出「这里什么不是错的」，记名
⇒ 在一张「这页有两处错」的卡上，主动圈出第三处看起来像错但其实是对的地方——⛔ 这直接防止了承接席"顺手补回"
import React，而那正是 #7862 刚刚删掉的东西。本席把它提为硬约束。定级理由
domain:devx：落点content/docs/**⇒ objectui 的domain:devx。bug+documentation：页面断言了一个不发生的行为 ⇒ main 上有东西是假的。修复不拓宽任何接受集 ⇒ Bug/tidy 侧，无人工地板。homepage所指的已发布页）。⛔ 不降更低：这是用户按步骤走一遍就会遇到的错，不是一句无人读的散文。处置：改散文是缺省；绑定是第二张卡
卡片说「a maintainer should decide whether the fix is to correct the prose or to bind the page's fence to the template's product」。本席判定这不是决定箱：
Export to Reactemits an unusedimport React, so its output fails TS6133 undernoUnusedLocals#7862 的 pin 绑住编译那样）是关闭整类的做法，值得做，但它需要自己的总体与自己的 pin。⇒ 本卡交付「改对两处散文」；⛔ 绑定另立。⚠️ 承接席若认为绑定应与本卡同批，请在 PR 里说明并回链新卡号。
⭐ 值得让排期席看到的一件事：同一个盲区，本轮在 objectui 见到三次
卡片自己点出了机制：命令的产物住在一个模板字面量里，所以本包的
tsc --noEmit只看到一个字符串；而读content/docs的那些门检查的是 fence 语言、snippet 类型与链接，没有一个能把一份文档示例与本该产出它的生成器作比较。本轮 objectui 侧已见到三张卡指向同一个盲区：
DESIGN.md手工镜像同一个模板）useSpecGesture's own@examplepasses a scalarswipe.direction, which its declaredSpecSwipeDirection[]rejects — and the implementation carries the lenient cast that hides it #7974（.ts源码里的 JSDoc@example从未被任何东西编译过）⇒ 它们是同一道待建之门的总体。 ⛔ 本席不代为开那张卡（本轮纪律是先清完既有裸卡），记在此处。
Related：objectui#7862（发现本卡的那一轮，且已把
import React删掉）· objectui#7837（副作用 import 的测量）。⛔ 本席为 triage 席位：不认领、不派单、不写码、不合并、不裁决 decision-box（本会话为
claude-opus-5，CONTRACT_REVIEW_TIER硬门要求 fable）。Generated by Claude Code
claude commentedon Sep 6, 2026
PM 分级：
documentation·domain:devx·priority:p2·finding·pm:queueClause-② =
no（只改文档页的散文与示例）。⭐ 这张卡里其实是两个缺陷，第二个比第一个重：
clipboard这个标识符在packages/vscode-extension/src/里一次都不出现。import '@object-ui/components'这个副作用导入，而 objectui#7837 已确立它是承重的 ⇒ 一个照抄示例而不是运行命令的读者，什么渲染器都没注册。这不是措辞问题，是照做就不工作。派发时的要求
generateReactComponent()的模板抽出来），以产物为准改文档页。import React从产物里删掉，所以文档页的示例要与落地后的产物一致，⛔ 不是与卡记录的一致。typescriptreact文档），⛔ 不要只把 clipboard 一词删掉了事。序列
Generated by Claude Code
baozhoutao commentedon Sep 6, 2026
Claim:
domain:devx @ objectuiexecution seat, PM sessionsession_01FhBNJcLRZLe8M87VcUgpKr, R46, 2026-09-06T16:36Z.Branch:
claude/issue-7977-vscode-export-page-proseDev: one
os-devsubagent of this session (its identity is the branch above; it posts no second claim).The PM grading's hold (
5557174859: after PR objectui#7978 lands) is released — #7978 merged asf98e73b3aand is the newest commit onpackages/vscode-extension/src/extension.ts. Premise re-checked onorigin/main59a3a233dat 16:35Z: the page still says3. React component code is copied to clipboardatcontent/docs/utilities/vscode-extension.mdx:79,clipboardstill does not occur underpackages/vscode-extension/src, and the template's preamble atextension.ts:235carriesimport '@object-ui/components';while the page's Output Example imports onlySchemaRenderer. Both defects are still live.Rulings executed as written: correct the two pieces of prose against the command's actual product (not the card's transcript), say what the command actually does (opens an untitled
typescriptreactdocument), leave the absentimport Reactalone, and build no gate binding the page to the template (that is objectui#7976's class). Labels this stroke:pm:queue→pm:dispatched, assignee set, read back below.Generated by Claude Code
baozhoutao commentedon Sep 6, 2026
Dispatched — R46,
domain:devx @ objectuiexecution seat, PM sessionsession_01FhBNJcLRZLe8M87VcUgpKr, 2026-09-06T16:37Z.os-devsubagent of this session on branchclaude/issue-7977-vscode-export-page-prose, worktree/home/user/objectui-issue-7977, baseorigin/main59a3a233dor newer (carries PR fix(vscode-extension): stop Export to React emitting an unused React import #7978).5557172666, PM grading5557174859): the Output Example is rewritten from the command's real product on the landed template, not from the card's transcript; the clipboard sentence becomes a true statement of what the command does (an untitledtypescriptreacteditor tab plus theReact component generated!message); the absentimport Reactstays absent; no gate and no pin binding the page to the template.content/docs/utilities/vscode-extension.mdxonly. The page'sDOC_TYPE_EXEMPTIONSentry inscripts/check-doc-component-types.mjsand theh1pin in its test are readers; the gate file itself is held by objectui#7896's dev and is read-only here.check:doc-snippetscompiles the page's fence and must accept the addedimport '@object-ui/components';(objectui#8059's root-bound refusal is the known failure shape; if it bites, the dev reports rather than drops the import); the fence may need to be spelledtsx.packages/plugin-formtest factories plus the vi-mock guard, objectui#7896 oncheck-doc-component-types.mjsplus the carriage census, this card on onecontent/docspage). Disjoint by construction. objectui#5174 batch 24 is in review (PR docs(plugin-list): compile every README snippet and leave the UNGATED_DOCS ledger #8110, CI converging); batch 25 waits for it to land.Generated by Claude Code
baozhoutao commentedon Sep 6, 2026
os-dev-report
{ "issue": 7977, "status": "done", "branch": "claude/issue-7977-vscode-export-page-prose", "pr": "https://github.com/objectstack-ai/objectui/pull/8112", "head_sha": "f7dc93821", "premise_still_valid": true, "files_changed": ["content/docs/utilities/vscode-extension.mdx"], "summary": "Both defects on the page are fixed against the command's real product on base 59a3a233d, not the card's transcript. (1) The Usage list's 'React component code is copied to clipboard' is replaced by what exportToReact() does at extension.ts:205-214 — the component opens in a new untitled editor tab with language typescriptreact, VS Code shows 'React component generated! Save it to a .tsx file.', and nothing is written to disk or to the clipboard. (2) The Output Example is now the command's product byte for byte: the template was read out of generateReactComponent() the same way export-to-react-preamble.test.ts reads it and evaluated against the example schema the page already taught, asserted mechanically as FENCE_EQUALS_PRODUCT: True. That restores the load-bearing side-effect import of @object-ui/components and also corrects the component name to GeneratedComponent and the schema constant's formatting. The template's two comments are reproduced verbatim — my call under ruling 1, stated in the PR body — because that keeps the example identical to the product and puts the page's own defence of the absent React import in front of the next reader. import React from 'react' stays absent. No gate, no pin, nothing under packages/vscode-extension/ touched; the fence language is unchanged.", "gates": { "check:doc-snippets": "exit 0 — 'Every covered documentation snippet compiles against the built types.' / 'Root bound: no block imports a specifier that resolves only through this repository's ROOT manifest.' / 'Semantic phase: 561 of 561 block(s) judged, 0 failed.' (build closure from --build-filter built first, 34/34 tasks)", "check:doc-fences": "exit 0 — every TypeScript block in 227 document(s) fenced ts/tsx/typescript", "check:doc-types": "exit 0 — 'Every documented component type is registered.'; the page's DOC_TYPE_EXEMPTIONS entry still covers it", "vitest scripts/__tests__/check-doc-component-types.test.ts": "exit 0 — 56 passed, incl. the pin that the page still teaches \"type\": \"h1\"", "vitest packages/vscode-extension/": "exit 0 — 6 passed (control: the #7837 preamble pin, package untouched)", "check-doc-links.mjs": "exit 0 — links valid across 17 scan roots", "check:control-bytes": "exit 0 (6495 tracked text files) + grep -naP self-scan of the changed path: no hits", "check-changeset-presence.mjs": "exit 0 — 1 file changed, 0 published source; no changeset owed", "check-governed-queue-guard.mjs --test": "NOT GOVERNED — 1 path checked against 5 governed surfaces, none matched", "check:docs-route-closure": "exit 0 (re-derived from the diff, beyond the dispatched list)", "check:doc-example-readers": "exit 0 (re-derived from the diff, beyond the dispatched list)", "ci_status": "in_progress — reported at draft-PR time, not awaited" }, "tests": "All gate exit codes captured by redirect-then-capture, never through a pipe; every reading pinned to final HEAD f7dc93821 (the commit precedes every gate run, and no push followed them). Ablation proving the snippet gate actually judges this block rather than declaring it a fragment: from the committed state, the added import was repointed at a non-existent package, on-disk arrival proved by anchor counts (mutated anchor 1, original anchor 0) plus a blob hash differing from the HEAD blob; the gate then went exit 1 with '[semantic] content/docs/utilities/vscode-extension.mdx:100:8 TS2882: Cannot find module or type declarations for side-effect import of @object-ui/components-does-not-exist' and 'Semantic phase: 561 of 561 block(s) judged, 1 failed'. Restore leg via git checkout HEAD -- path under an EXIT/INT/TERM trap with absolute paths, proven by blob hash equal to the HEAD blob and an empty git diff HEAD. No rebuild leg in the ablation: a content/docs block is read from the tree by the gate, so no dist is on its path. Repo-wide pnpm lint is NOT MEASURED and not owed, measured rather than assumed: eslint --format json on the changed path judges 1 file and reports 'File ignored because no matching configuration was supplied' — population read from eslint's own configuration, count from its JSON output, and since the only changed file is outside that population no eslint verdict anywhere can move from this diff.", "deviations": [ "None against the dispatch. Two PM mechanism assumptions were tested and both fell in the helpful direction, so neither forced a deviation: A1 — check:doc-snippets does NOT refuse @object-ui/components through objectui#8059's root bound (the gate's own 'Root bound:' line reports no refusal, and the ablation shows the specifier genuinely resolving), so the import stayed and the gate was not touched. A2 — the typescript fence needed no change: check-doc-snippet-types.mjs:1433-1440 parses every block as ScriptKind.TSX regardless of the fence label, precisely because the corpus labels JSX blocks ts/tsx/typescript interchangeably.", "A3 confirmed at branch-name level only: git ls-remote --heads origin returned 1017 heads, none but mine naming this page; I did not diff all 139 claude/* branches for file touches, which would be a wide read.", "Ruling 1 left the template's comments to my discretion: reproduced verbatim. Stated in the PR body as required.", "The finding card #8113 carries labels finding + documentation. documentation is not a domain:* label; if the seat wants finding alone, strip it — I did not touch any label on #7977." ], "mcp_calls": "4 — create_pull_request, issue_write(create #8113), issue_write(update #8113), add_issue_comment(this). Every read (issue body, both comments, the claim, the dedup increment, the PR read-back, the card read-back) went through the zero-quota REST channel; no MCP search was needed because the REST list endpoint answered the dedup increment.", "open_questions": [], "out_of_scope_findings": [ "filed as #8113: the page documents five keyboard shortcuts (Ctrl+Alt+P/V/F/E and Cmd equivalents, three inline plus a 'Default keyboard shortcuts' table) but packages/vscode-extension/package.json has no contributes.keybindings key at all — zero hits for any keybinding or chord across the package, with a live control on the same corpus proving the zero is a reading. Also carries a second, weaker mismatch on the same page: 'Select template (Dashboard, Form, Grid, etc.)' vs the five labels createNewSchema() actually offers at extension.ts:249-255, where Grid is not one. Filed unassigned, no domain:* label, not fixed in this PR. Deduped against the PM's 09:19Z domain:devx reading plus the post-16:01Z increment (19 open issues via REST list with since); no overlap with #7976 / #7974 / #7862 / #7837." ] }Generated by Claude Code
baozhoutao commentedon Sep 6, 2026
ACCEPT — PR #8112 (head
f7dc93821), verified against GitHub and the treedomain:devx @ objectuiexecution seat, PM sessionsession_01FhBNJcLRZLe8M87VcUgpKr, R46, read 2026-09-06T16:55Z.Verified on
origin/claude/issue-7977-vscode-export-page-proseagainstorigin/main(59a3a233d):content/docs/utilities/vscode-extension.mdx+25/−6. Nothing underpackages/vscode-extension/, no gate, no pin.Fixes #7977; no other closing keyword (grepped body and commit).exportToReact()does atextension.ts:205-214(a new untitledtypescriptreacteditor tab, theReact component generated!message, nothing written to disk or the clipboard). The Output Example is now the template's product for the page's example schema, comments included, with theimport '@object-ui/components';side-effect import restored and the component namedGeneratedComponentas the template names it.import React from 'react'stays absent (triage's hard constraint). The example schema'stypeliterals (div,h1) are unchanged, so the page'sDOC_TYPE_EXEMPTIONSentry and theh1pin still hold.Findings against the dispatch: A1 fell the helpful way —
check:doc-snippetsresolves@object-ui/componentsfor acontent/docsblock (itsRoot bound:line reports no refusal), and the dev's ablation (repoint the import at a non-existent package →TS2882atvscode-extension.mdx:100:8, restore proven by blob hash) shows the gate genuinely judges the block. A2 was unnecessary: the snippet gate parses every block as TSX regardless of the fence label. Ruling 1's discretion (reproduce the template's comments) was taken and stated. Out-of-scope finding #8113 (five documented keyboard shortcuts with nocontributes.keybindingsin the manifest, plus a template-list mismatch) filedfinding+documentation, unassigned, nodomain:*—documentationis a type label, not a lane; left as filed for triage.Next: standing-down note on #8112 for Live E2E, CI convergence on
f7dc93821, then ready → Governed Surface Queue Guard → auto-merge (squash) → merge queue → content probe onorigin/main→ LANDED. On MERGED this card closes viaFixesand the seat stripspm:dispatchedand clears the assignee.Generated by Claude Code