Repository navigation
Conversation
…anscript A spec carried by an assistant message rendered read-only. generativeUi on MessageList and Chat now takes handlers, store and onRenderEvent. With any of them the tree is interactive: handlers run the actions a spec names, each message keeps state of its own seeded from its spec, or every spec shares the store the application passes, and onRenderEvent reports each event with the ID of its message. A registry alone stays read-only.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
enabled auto-merge
November 16, 2026 05:50
Contributor
Author
|
🤖 Posted by Claude Code |
blove
added this pull request to the merge queue
Nov 16, 2026
Any commits made after this event will not be merged.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A json-render spec carried by an assistant message rendered read-only in the React transcript (#1604), while
RenderSpecitself gained actions and state writes in #1605. This connects the two, opt-in, throughgenerativeUionMessageListandChat:handlers: the actions a spec'sonbindings may run. A binding naming an action that was not supplied does nothing.store: one application-owned state owner shared by every spec, in place of each spec's ownstate.onRenderEvent: reports each action, state write and reported result as{ messageId, event }(new exported typeMessageRenderEvent).With any of the three set, views get
emitandset. Withoutstore, each message keeps state of its own, seeded from its spec'sstateonce that finishes streaming and dropped with its row, so two messages carrying the same spec do not share edits. This matches the Angular chat, which passes only an explicit consumer store and otherwise lets each surface seed its own.A
registryalone behaves exactly as before: read-only.renderable()now keeps an element'sonbindings, which it previously dropped.Verification
npx nx run-many -t test,type-tests,lint,build -p react,content,core: passed (81 React test files, 1391 tests).node scripts/react-parity/verify-packages.mjs: passed.node scripts/react-parity/verify-boundaries.mjs: passed (the chat entry now imports@threadplane/content/render-stateat runtime).node scripts/react-parity/inventory.mjs --check --drift warn: passed (baseline drift is informational).node --test scripts/react-parity/{verify-packages,runtime-consumer,inventory}.spec.mjs: 169 pass.node scripts/react-parity/verify-langgraph-candidate.mjs: rerun in progress when this was opened; result to follow in a comment.Not checked in a browser.
🤖 Generated with Claude Code