Re-export reqwest crate (#158)
* Re-export reqwest crate In a large project, it's not unheard of for multiple mutually-incompatible versions of a major crate like `reqwest` to end up in the mix. By re-exporting the version of `reqwest` used by `reqwest-middleware`, we can be sure we're referring to the *correct* `reqwest`, rather than some other, incompatible, `reqwest`. * Update CHANGELOG.md --------- Co-authored-by: Ethan Brierley <ethanboxx@gmail.com>pull/166/head
parent
226562735c
commit
524e044fd7
|
@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||||
|
|
||||||
### Added
|
### Added
|
||||||
- Added support for `opentelemetry` version `0.23`.
|
- Added support for `opentelemetry` version `0.23`.
|
||||||
|
- Added re-export of `reqwest`.
|
||||||
- `http2`, `rustls-tls`, and `charset` features, which simply enable those features in `reqwest`.
|
- `http2`, `rustls-tls`, and `charset` features, which simply enable those features in `reqwest`.
|
||||||
|
|
||||||
## [0.3.1]
|
## [0.3.1]
|
||||||
|
|
|
@ -58,3 +58,4 @@ pub use client::{ClientBuilder, ClientWithMiddleware, RequestBuilder};
|
||||||
pub use error::{Error, Result};
|
pub use error::{Error, Result};
|
||||||
pub use middleware::{Middleware, Next};
|
pub use middleware::{Middleware, Next};
|
||||||
pub use req_init::{Extension, RequestInitialiser};
|
pub use req_init::{Extension, RequestInitialiser};
|
||||||
|
pub use reqwest;
|
||||||
|
|
Loading…
Reference in New Issue