fix(error): preserve unwrapped API error bodies#1897
Open
vixco wants to merge 1 commit into
Open
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
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.
Changes being requested
Preserve JSON error response bodies that do not use the OpenAI { error: ... } wrapper. Today those responses produce an APIError with error === undefined even though the response body was valid JSON. This keeps the existing behavior for wrapped OpenAI errors, while falling back to the full parsed body when the error key is absent.
Additional context & links
Fixes #1577.
Tests:
Note:
ode ./node_modules/typescript/bin/tsc currently fails in this local checkout because example files import optional packages that are not installed here (@azure/identity, express,
ext).