Created by: whirm
Add support for reqwest-middleware (only when async support is enabled).
With this, one can easily add middleware which add features like tracing or retries to the client requests:
use petstore_async::apis::configuration::Configuration;
use reqwest::Identity;
use reqwest_middleware::ClientBuilder;
use reqwest_tracing::TracingMiddleware;
let config = Configuration {
client: ClientBuilder::new(reqwest::ClientBuilder::new().build()?)
.with(TracingMiddleware::default())
.build(),
..Configuration::default()
}
Not sure if this would be considered a breaking change or not as it changes the Configuration struct signature. Let me know if I need to retarget the PR.
@frol, @farcaller, @richardwhiuk, @paladinzh, @jacob-pro: Pinging you as requested on the PR template :)
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(6.3.0) (minor release - breaking changes with fallbacks),7.0.x(breaking changes without fallbacks) -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.