Fix: Handle usage.prompt_tokens_details when missing or None in API r… #69
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.
…esponse
Fix NoneType issue for usage.prompt_tokens_details in API responses
Some API responses omit the
prompt_tokens_details
field or set it toNone
, causing downstream code to throw AttributeError when accessed directly.This change ensures that
usage.prompt_tokens_details
defaults to an empty dictionary{}
when missing or None, preventing runtime errors and improving compatibility across models and endpoints.convert_to_openai_object
to normalize missing fieldsChanges being requested
Additional context & links