Adopt middleware-enabled generated Rust API clients - #14
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.
OASmith's generated Rust clients now accept a middleware-enabled HTTP client so applications can configure automatic trace propagation once at construction: responsibleapi/oasmith#16.
Regenerate the public API client, add
reqwest-middleware, and update the sync engine and CLI request-builder types to match. Preserve the existing HTTP configuration, cancellation handling, response decoding, and URL redaction. This updates the consumer contract; it does not configure an OpenTelemetry SDK in the application.Validation: regenerated through
moon run openapi:generate-public-rust-client;moon run cli:test client-engine:testpassed, including all 16 sync-engine tests and CLI compilation.