Make object field in openai-compatible response optional#190
Merged
dongri merged 4 commits intodongri:mainfrom Oct 31, 2025
Merged
Make object field in openai-compatible response optional#190dongri merged 4 commits intodongri:mainfrom
dongri merged 4 commits intodongri:mainfrom
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
2 participants
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 is a remake of #189 which will be closed because I used the wrong branch)
So the zAI API claims to be compatible with the OpenAI chat completion API, but for whatever reason it does not include an "object" field in the response. In its current state openai-api-rs requires this field to be present, so it was breaking when using zAI APIs.
This change makes the field optional, allowing the lib to successfully deserialize responses from zAI.