Skip to content

fix(useAiChatStream): send message field name to match OR#201

Merged
rubenvdlinde merged 1 commit into
betafrom
fix/widget-message-field-name
May 11, 2026
Merged

fix(useAiChatStream): send message field name to match OR#201
rubenvdlinde merged 1 commit into
betafrom
fix/widget-message-field-name

Conversation

@rubenvdlinde
Copy link
Copy Markdown
Contributor

Pairs with openregister#1466. Widget was sending content: but OR's ChatStreamController reads message: (matches the existing non-streaming /api/chat/send shape per hydra ADR-034). Every stream request returned {isError: true, error: missing_message} and the assistant bubble never rendered. Fix sends both message and content (alias) for rollout safety; OR ignores unknown keys.

Verified end-to-end: SSE returns a populated final event with the qwen3.5 reply; user message + assistant bubble both render in decidesk.

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.
@rubenvdlinde rubenvdlinde merged commit 4ab57b5 into beta May 11, 2026
@rubenvdlinde rubenvdlinde deleted the fix/widget-message-field-name branch May 11, 2026 18:44
@github-actions
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.0.0-beta.31 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant