cargo fmt and cargo clippy

zcash_client_backend/src/data_api/testing/transparent.rs

@@ -20,7 +20,7 @@ use zcash_protocol::local_consensus::LocalNetwork;
 
 use super::TestAccount;
 /// checks whether the transparent balance of the given test [`account`] is as [`expected`]
-/// considering the [`min_confirmations`]. It is assumed that zero or one [`min_confirmations`] 
+/// considering the [`min_confirmations`]. It is assumed that zero or one [`min_confirmations`]
 /// are treated the same so this function also checks the other case when 1 or 0 [`min_confirmations`]
 /// are passed as arguments.
 fn check_balance<DSF>(
@@ -66,8 +66,8 @@ fn check_balance<DSF>(
         Some(expected.spendable_value()),
     );
 
-    // we currently treat min_confirmations the same regardless they are 0 (zero confirmations) 
-    // or 1 (one block confirmation). We will check if this assumption holds until it's no 
+    // we currently treat min_confirmations the same regardless they are 0 (zero confirmations)
+    // or 1 (one block confirmation). We will check if this assumption holds until it's no
     // longer made. If zero and one [`min_confirmations`] are treated differently in the future,
     // this check should then be removed.
     if min_confirmations == 0 || min_confirmations == 1 {
@@ -81,7 +81,6 @@ fn check_balance<DSF>(
             Some(expected.spendable_value()),
         );
     }
-
 }
 
 pub fn put_received_transparent_utxo<DSF>(dsf: DSF)
@@ -355,14 +354,14 @@ where
 
     // Add one extra block
     st.generate_empty_block();
-    
+
     // Scan that block
     st.scan_cached_blocks(height, 1);
 
     // now we generate one more block and the balance should be the same as when the
     // check_balance function was called with zero or one confirmation.
     st.generate_empty_block();
-    st.scan_cached_blocks(height + 1 , 1);
+    st.scan_cached_blocks(height + 1, 1);
 
     check_balance::<DSF>(&st, &account, taddr, 2, &zero_or_one_conf_value);
 }