From 28a13232c026e217f17c344196f41f7982b64fb7 Mon Sep 17 00:00:00 2001 From: Ethan Brierley Date: Thu, 17 Oct 2024 09:52:55 +0100 Subject: [PATCH] docs: fix spelling `clonable` -> `cloneable` (#191) --- reqwest-retry/src/middleware.rs | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/reqwest-retry/src/middleware.rs b/reqwest-retry/src/middleware.rs index ccf5b94..f84015e 100644 --- a/reqwest-retry/src/middleware.rs +++ b/reqwest-retry/src/middleware.rs @@ -56,14 +56,14 @@ macro_rules! log_retry { /// /// This middleware always errors when given requests with streaming bodies, before even executing /// the request. When this happens you'll get an [`Error::Middleware`] with the message -/// 'Request object is not clonable. Are you passing a streaming body?'. +/// 'Request object is not cloneable. Are you passing a streaming body?'. /// /// Some workaround suggestions: /// * If you can fit the data in memory, you can instead build static request bodies e.g. with /// `Body`'s `From` or `From` implementations. /// * You can wrap this middleware in a custom one which skips retries for streaming requests. /// * You can write a custom retry middleware that builds new streaming requests from the data -/// source directly, avoiding the issue of streaming requests not being clonable. +/// source directly, avoiding the issue of streaming requests not being cloneable. pub struct RetryTransientMiddleware< T: RetryPolicy + Send + Sync + 'static, R: RetryableStrategy + Send + Sync + 'static = DefaultRetryableStrategy, @@ -149,7 +149,8 @@ where // since the byte abstraction is a shared pointer over a buffer. let duplicate_request = req.try_clone().ok_or_else(|| { Error::Middleware(anyhow!( - "Request object is not clonable. Are you passing a streaming body?".to_string() + "Request object is not cloneable. Are you passing a streaming body?" + .to_string() )) })?;