Preserve emoji characters in structured output payloads#2691
Uh oh!
There was an error while loading. Please reload this page.
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.
Changes being requested
ensure_ascii=FalseContent-Type: application/jsonheaderchat.completions.parserequest and verifies the schema still contains plain emojisAdditional context & links
Structured outputs that include Pydantic schemas were being serialized with
ensure_ascii=True, so emojis (and other non-BMP characters) arrived as surrogate escapes (e.g.,\ud83d\ude0d). After this change the payload stays UTF‑8, preserving the characters end-to-end.