fix (examples): avoid mixed message types in use-chat-streamdata-multistep
#5824
Conversation
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
lgrammel
approved these changes
Apr 17, 2025
|
great find! please also update |
samdenty
pushed a commit
that referenced
this pull request
Apr 22, 2025
…tistep` (#5824) Co-authored-by: Lars Grammel <[email protected]>
samdenty
added a commit
that referenced
this pull request
Apr 22, 2025
…tistep` (#5824) (#5886) Co-authored-by: Grace Yun <[email protected]> Co-authored-by: Lars Grammel <[email protected]>
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.
Background
Example was broken due to mixing Core + UI messages in the second
streamTextcallSummary
Convert UI messages (from hook) to Core Message before merging with assistant messages from first
streamTextcallTasks
pnpm prettier-fixto fix any formatting issuesFuture Work