Refactor schema system to support provider-specific constraints #130
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.
Description
Refactors the schema constraint system to enable provider-specific implementations through a plugin architecture. Each LLM provider can now define its own optimal approach for structured output generation while maintaining backward compatibility.
Related to #128, #59, #99
Feature
How Has This Been Tested?
Verified backward compatibility with existing providers and tested schema generation with multiple providers.
Checklist:
Code of conduct.
Contributing
page, and I either signed the Google
Individual CLA
or am covered by my company's
Corporate CLA.
issue(s) and we have agreed upon the general approach.
issue(s) that documentation elsewhere needs updating.
Google's Python Style Guide
and ran
pylint
over the affected code.Key Changes
Schema Abstraction (
langextract/schema.py
)BaseSchema
abstract class for provider-specific implementationsFormatModeSchema
for JSON/YAML providers (OpenAI, Ollama)Factory Integration (
langextract/factory.py
)create_model()
with schema constraint supportProvider Schemas (
langextract/providers/schemas/
)GeminiSchema
to dedicated moduleTesting
Breaking Changes
None - full backward compatibility maintained. The refactoring is entirely internal with no changes to public APIs.