Repository navigation
docs: add multi-language response type examples - #191
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
- compare existing type composition and target-specific response declarations - distinguish optional keys and singleton status constraints across languages - exercise the example through focused assertions and the example smoke suite
adamcavendish
force-pushed
the
adamcavendish/response-type-examples
branch
from
October 19, 2026 12:23
c2b914a to
3cadf5a
Compare
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.
Summary
Add
cargo run --example response_typesto compare response field representations using existing APIs:Recordintersections andPartialTypedDictwithNotRequiredThe example prints all generated sources or writes them to a supplied directory. Focused tests protect TypeScript import aliases and optional-key composition, native fragment syntax, and named declarations. Run instructions live in the example itself, and the smoke suite runs it.
Boundaries
200; other targets use ordinary integer fields.Rawescape hatch.