Repository navigation
Preserve Pydantic metadata and native root schemas - #163
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
vrslev
marked this pull request as ready for review
November 2, 2026 13:46
vrslev
enabled auto-merge (squash)
November 2, 2026 13:47
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.
Agent:
With
api_metadata_enabled=True, the Litestar bootstrapper retains Pydantic model docstrings andField(description=...)metadata on TypedDict properties. RootModel schemas describe the actual scalar, array or object value, including nested and recursive roots, while preserving native constraints and explicit model and use-site examples. The health probe describes its static checks directly on its handler.The metadata fallback uses the initialized schema providers, preserving instrument-supplied aliases and schema owners installed by initialization plugins. Explicit descriptions and custom schema plugins retain precedence. Validation and serialization remain unchanged.
38 focused schema/HTTP tests pass, including recursion, aliases, examples and plugin ownership. The three schema helpers have 100% coverage. Repository CI lint and tests pass on Linux, macOS and Windows across Python 3.10–3.15.