Add usage to final chunk for deepinfra#1041
Merged
VisargD merged 2 commits intoApr 22, 2025
Merged
Conversation
narengogi
approved these changes
Apr 21, 2025
narengogi
reviewed
Apr 21, 2025
| finish_reason: parsedChunk.choices[0].finish_reason, | ||
| }, | ||
| ], | ||
| usage: parsedChunk.usage |
Member
There was a problem hiding this comment.
this could simply be parsedChunk.usage imo
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
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.
Author Description
(optional)
Title: Add usage to final chunk for deepinfra
🔄 What Changed
usagefield to theDeepInfraStreamChunkinterfaceDeepInfraChatCompleteStreamChunkTransformfunction to include usage data in the transformed output when available🔍 Impact of the Change
📁 Total Files Changed
src/providers/deepinfra/chatComplete.ts(+12 lines, -0 lines)🧪 Test Added
🔒 Security Vulnerabilities
Related Issues: N/A
Quality Recommendations
Add unit tests to verify the correct handling of usage information in streaming responses
Consider adding documentation comments to explain the purpose of the usage field and how it's used
Add error handling for potential malformed usage data from the API