feat: structured input types (dataclass, TypedDict, NamedTuple, Enum)#6
Merged
Conversation
Parameters typed as a dataclass, TypedDict, NamedTuple, or Enum now generate proper nested JSON Schema objects (or typed enums) across all four providers. Nesting is recursive; self-referential types are guarded against infinite recursion. Also fixes the Gemini formatter dropping 'required' on nested objects. Bumps to 0.2.0 (also carries the author-email metadata removal).
lavrut
marked this pull request as ready for review
July 1, 2026 03:37
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.
Validation PR to exercise the full CI matrix before the 0.2.0 release.
What changed
dataclass,TypedDict,NamedTuple,Enum→ nested JSON Schema objects / typed enums, across all 4 providers.requiredon nested objects.Local verification