fix(types): export new Responses API types for OpenAI namespace #1395
Conversation
This file contains 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
davidchicano
changed the title
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.
Changes being requested
This PR adds complete type exports for the new Responses API in the OpenAI namespace. Currently, only the
Responsesclass is exported, but the interface types and associated classes that developers need to properly use this API with TypeScript are missing.The changes include:
./resources/responses/responses.tsResponseStreamfrom./lib/responses/ResponseStream.tsOpenAInamespace using the same structure as other APIsAdditional context & links
The Responses API is OpenAI's new flagship API that will eventually replace ChatCompletions, so having complete TypeScript types is crucial for developers to properly migrate.
This change follows the same export pattern used for ChatCompletions and other APIs, ensuring consistency across the library and improving the TypeScript development experience.