Connect supported SDK to generated OpenAPI wire types - #3
Merged
Merged
Conversation
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.
Regeneration previously updated a separate reference client while the supported SDK kept handwritten wire fields. The supported History, profile and webhook readers now consume schema-derived field types, with generated request metadata or explicit transport compatibility guards.
The typed boundary retains raw JSON for the existing normalization rules. Incompatible consumed fields, unsupported required parameters, parameter-location changes and webhook envelope changes fail the contract checks. The generated reference transport remains separate.
Validation: 350 tests; 23 compiler/generation mutation cases plus required-parameter, route and ping boundary regressions; packaged JAR consumer. Generation freshness, full native build and independent source review passed. The public resource schema and package version are unchanged. Registry publication is a separate step.