fix(types): make ChatCompletionMessageToolCallParam instantiable #2543
+56
−6
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.
Summary
Fixes issue where
ChatCompletionMessageToolCallParam
could not be instantiated after version 1.99.2, causingTypeError: Cannot instantiate typing.Union
.This addresses:
Problem
In version 1.99.2,
ChatCompletionMessageToolCallParam
was changed from a concreteTypedDict
class to aUnion
type alias to support custom tool calls. This broke backward compatibility for users who were directly instantiating the type.Before (v1.99.1):
After (v1.99.2+):
Solution
This change introduces a constructor class that can be instantiated while preserving the Union type behavior for type checking:
ChatCompletionMessageToolCallParam()
now works againChanges Made
_ChatCompletionMessageToolCallParamConstructor
with proper overloadsChatCompletionMessageToolCallParamType
for explicit typingtype="function"
inference for pre-1.99.2 patterns__init__.py
Test Plan
🤖 Generated with Claude Code