From 07324e268b7428d3ca26eaccc1a4dcb11d29f128 Mon Sep 17 00:00:00 2001
From: Zhengchao An <anzhengchao@gmail.com>
Date: Wed, 8 Jul 2026 08:01:13 +0800
Subject: [PATCH] fix(protocols): allow clippy::type_complexity in expiration
 worker tests (#4395)

fix(protocols): allow clippy type_complexity in test mock struct

The MockExpirationObjectBackend test struct uses a nested generic type
that triggers clippy::type_complexity. Add #[allow(clippy::type_complexity)]
since this is test-only code where the type is inherent to the mock design.

Co-authored-by: houseme <housemecn@gmail.com>
---
 crates/protocols/src/swift/expiration_worker.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/crates/protocols/src/swift/expiration_worker.rs b/crates/protocols/src/swift/expiration_worker.rs
index 079e5335d..164b694c0 100644
--- a/crates/protocols/src/swift/expiration_worker.rs
+++ b/crates/protocols/src/swift/expiration_worker.rs
@@ -659,6 +659,7 @@ mod tests {
     type MetadataResult = SwiftResult<Option<HashMap<String, String>>>;
 
     #[derive(Default)]
+    #[allow(clippy::type_complexity)]
     struct MockExpirationObjectBackend {
         metadata_results: Mutex<VecDeque<MetadataResult>>,
         delete_results: Mutex<VecDeque<SwiftResult<()>>>,