Add static file infrastructure for generated clients #125
+105
−0
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
This PR adds the foundational infrastructure for including static Python files in generated clients. This capability is essential for the enhanced error handling feature (#100) which requires shared utilities and exception classes.
Changes
Core Infrastructure
static_files: List[StaticFile]fieldTests
How It Works
Static files are:
generate_static_files()ConversionResultapi_config.py)Use Case: Issue #100
This infrastructure enables the enhanced error handling feature by allowing us to ship:
errors.py: Exception hierarchy (APIError, ClientError, ServerError)response.py: DetailedResponse wrapper with fluent APIutils.py: Helper functions (unwrap, expect, match, type guards)These modules will be shared across all generated services without requiring template generation.
Testing
✅ All existing tests pass (257 tests)
✅ New tests verify static file generation
✅ Backwards compatible (empty list by default)
✅ 95%+ code coverage maintained
Status
Related