fix: preserve canonical chat completions providerData fields#1064
Merged
fix: preserve canonical chat completions providerData fields#1064
Conversation
🦋 Changeset detectedLatest commit: b8b6723 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
This pull request fixes the Chat Completions converter so provider-specific metadata can still flow through without overwriting the canonical message and tool-call envelopes that the SDK constructs. It adds reserved-key filtering for content parts, message-level providerData, built-in
file_search_callreplay, function call replay, and function call results, and adds regression coverage for both the helper and the converter paths. The behavior change is intentionally narrow: extra providerData is still preserved, but fields such asrole,content,tool_calls, nested functionname, nested functionarguments, and tool resulttool_call_idcan no longer silently replace the SDK-authored values.