Repository navigation
feat: dogfood React Chat Input in the native example - #1258
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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
1 participant
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.
The Chat Input documentation can now run a native React example against the existing aviation chat graph. It demonstrates custom placeholders, Enter and Ctrl/Command+Enter shortcuts, disabled input, editable drafts while streaming, Stop, and local conversation reset. Drafts survive response confirmation and asynchronous cleanup; competing submissions are blocked.
The example uses the existing React components and transport with explicit canonical history confirmation. Title generation is excluded from visible message streaming. React Docs, Code, and Run are available on the canonical page, with Angular remaining the default.
Validation: 22 native suites (1,098 unit tests and 326 installed browser scenarios), production website browser suite (286 passed, 4 expected skips), 63 frontend assembly and 22 native HTTP routes, strict TypeScript, lint, compiled graph tests, parity inventory, and isolated package consumers. Desktop and mobile screenshots were inspected. The new example has 33 unit tests and 18 installed browser scenarios, plus five website embedding journeys.