Type report responses as JSON - #3223
Merged
Merged
Conversation
adamtheturtle
force-pushed
the
type-report-json
branch
from
September 10, 2026 15:12
91a7382 to
11dfd43
Compare
adamtheturtle
temporarily deployed
to
development
September 10, 2026 15:12 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
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
1 participant
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.
Report constructors consume decoded API responses, so type them as recursive JSON values instead of arbitrary
objectvalues.This also promotes the existing JSON value alias to a documented public module so public annotations do not expose a private implementation detail. The malformed-response test continues to exercise the public
QueryResultconstructor.The Model Target response validation from #3222 is now merged.