fix(useAiChatStream): send message field name to match OR#201
Merged
Conversation
OR's ChatStreamController (PR #1466) reads `$body['message']` to match
the existing /api/chat/send shape. The widget was sending `content:`,
so every stream request returned `{isError: true, error: missing_message}`
and the assistant bubble never rendered.
Send both `message` and `content` (alias) so the widget stays
compatible across the rollout window. OR's controller ignores unknown
keys.
Contributor
|
🎉 This PR is included in version 1.0.0-beta.31 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Pairs with openregister#1466. Widget was sending
content:but OR's ChatStreamController readsmessage:(matches the existing non-streaming/api/chat/sendshape per hydra ADR-034). Every stream request returned{isError: true, error: missing_message}and the assistant bubble never rendered. Fix sends bothmessageandcontent(alias) for rollout safety; OR ignores unknown keys.Verified end-to-end: SSE returns a populated
finalevent with the qwen3.5 reply; user message + assistant bubble both render in decidesk.