Repository navigation
feat(react): support previous message role context and spacing - #1498
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Custom message renderers can now forward the immediately preceding projected row's role to
ChatMessage. This preserves assistant-to-user spacing through wrappers and updates the following row when its predecessor changes, while unrelated historical rows retain memoized rendering. Omitted context retains the existing sibling fallback; explicit context takes precedence.The native example dogfoods primitive
prevRoleforwarding. The readonly optional prop and row-context field preserve one-argument renderers, enriched row inference, rich content ownership, scrolling, and current/streaming indicators. Guides and generated API snapshots describe the bounded spacing behavior; automatic control reveal and full T23 parity remain open.Validation:
skipLibCheck:false, and 28 browser scenarios passed, including wrapped/default rows, explicit precedence, and LTR/RTL computed spacing. All previous corruption guards remain; package tooling passed 100 tests.