style: run formatter on comments and doc strings

Author: fewerner

crypto-ffi/src/core_crypto_context/mls.rs

@@ -379,7 +379,8 @@ impl CoreCryptoContext {
 
     /// Get all credentials from this client which match the provided parameters.
     ///
-    /// Parameters which are unset or `None` match anything. Those with a particular value find only credentials matching that value.
+    /// Parameters which are unset or `None` match anything. Those with a particular value find only credentials
+    /// matching that value.
     pub async fn find_credentials(
         &self,
         client_id: Option<ClientIdMaybeArc>,

crypto-ffi/src/core_crypto_context/proteus.rs

@@ -105,7 +105,8 @@ impl CoreCryptoContext {
         proteus_impl!({ self.inner.proteus_new_prekey(prekey_id).await.map_err(Into::into) })
     }
 
-    /// Creates a new Proteus prekey with an automatically incremented ID and returns the CBOR-serialized version of the prekey bundle
+    /// Creates a new Proteus prekey with an automatically incremented ID and returns the CBOR-serialized version of the
+    /// prekey bundle
     ///
     /// Warning: The Proteus client **MUST** be initialized with `proteus_init` first or an error will be returned
     ///

crypto-ffi/src/credential.rs

@@ -10,7 +10,8 @@ use crate::{Ciphersuite, CoreCryptoResult, CredentialType, client_id::ClientIdMa
 /// This is tied to a particular client via either its client id or certificate bundle,
 /// depending on its credential type, but is independent of any client instance or storage.
 ///
-/// To attach to a particular client instance and store, see [`CoreCryptoContext::add_credential`][crate::CoreCryptoContext::add_credential].
+/// To attach to a particular client instance and store, see
+/// [`CoreCryptoContext::add_credential`][crate::CoreCryptoContext::add_credential].
 #[derive(Debug, Clone, derive_more::From, derive_more::Into, uniffi::Object)]
 pub struct Credential(pub(crate) CryptoCredential);
 

crypto-ffi/src/decrypted_message.rs

@@ -18,7 +18,8 @@ pub struct DecryptedMessage {
     /// Commit delay in seconds.
     ///
     /// When set, clients must delay this long before processing a commit.
-    /// This reduces load on the backend, which otherwise would receive epoch change notifications from all clients simultaneously.
+    /// This reduces load on the backend, which otherwise would receive epoch change notifications from all clients
+    /// simultaneously.
     pub commit_delay: Option<u64>,
     /// [ClientId] of the sender of the message being decrypted. Only present for application messages.
     pub sender_client_id: Option<ClientIdMaybeArc>,
@@ -76,7 +77,8 @@ pub struct BufferedDecryptedMessage {
     /// Commit delay in seconds.
     ///
     /// When set, clients must delay this long before processing a commit.
-    /// This reduces load on the backend, which otherwise would receive epoch change notifications from all clients simultaneously.
+    /// This reduces load on the backend, which otherwise would receive epoch change notifications from all clients
+    /// simultaneously.
     pub commit_delay: Option<u64>,
     /// [ClientId] of the sender of the message being decrypted. Only present for application messages.
     pub sender_client_id: Option<ClientIdMaybeArc>,

crypto-ffi/src/e2ei/acme_challenge.rs

@@ -4,12 +4,14 @@
 /// - See [core_crypto::e2e_identity::types::E2eiAcmeChallenge]
 #[derive(Debug, Clone, uniffi::Record)]
 pub struct AcmeChallenge {
-    /// Contains raw JSON data of this challenge. This is parsed by the underlying Rust library hence should not be accessed
+    /// Contains raw JSON data of this challenge. This is parsed by the underlying Rust library hence should not be
+    /// accessed
     pub delegate: Vec<u8>,
     /// URL of this challenge
     pub url: String,
     /// Non-standard, Wire specific claim. Indicates the consumer from where it should get the challenge proof.
-    /// Either from wire-server "/access-token" endpoint in case of a DPoP challenge, or from an OAuth token endpoint for an OIDC challenge
+    /// Either from wire-server "/access-token" endpoint in case of a DPoP challenge, or from an OAuth token endpoint
+    /// for an OIDC challenge
     pub target: String,
 }
 

crypto-ffi/src/e2ei/mod.rs

@@ -15,7 +15,8 @@ pub enum E2eiConversationState {
     Verified = 1,
     /// Some clients are either still Basic or their certificate is expired
     NotVerified,
-    /// All clients are still Basic. If all client have expired certificates, [E2eiConversationState::NotVerified] is returned.
+    /// All clients are still Basic. If all client have expired certificates, [E2eiConversationState::NotVerified] is
+    /// returned.
     NotEnabled,
 }
 

crypto-ffi/src/error/mls.rs

@@ -33,8 +33,8 @@ pub enum MlsError {
     #[error("The received commit is deemed stale and is from an older epoch.")]
     StaleCommit,
     /// This happens when the DS cannot flag KeyPackages as claimed or not. In this scenario, a client
-    /// requests their old KeyPackages to be deleted but one has already been claimed by another client to create a Welcome.
-    /// In that case the only solution is that the client receiving such a Welcome tries to join the group
+    /// requests their old KeyPackages to be deleted but one has already been claimed by another client to create a
+    /// Welcome. In that case the only solution is that the client receiving such a Welcome tries to join the group
     /// with an External Commit instead
     #[error(
         "Although this Welcome seems valid, the local KeyPackage it references has already been deleted locally. Join this group with an external commit"

crypto-ffi/src/identity/x509.rs

@@ -1,6 +1,7 @@
 use std::time::{Duration, SystemTime};
 
-/// Represents the parts of [WireIdentity][crate::WireIdentity] that are specific to a X509 certificate (and not a Basic one).
+/// Represents the parts of [WireIdentity][crate::WireIdentity] that are specific to a X509 certificate (and not a Basic
+/// one).
 ///
 /// We don't use an enum here since the sole purpose of this is to be exposed through the FFI (and
 /// union types are impossible to carry over the FFI boundary)

crypto/benches/commit.rs

@@ -71,7 +71,8 @@ fn commit_add_n_clients_bench(c: &mut Criterion) {
 }
 
 /// Benchmark to measure the impact of group size on the runtime of creating and merging a remove commit.
-/// Number of removed clients is equal to group size (→ all clients except the initial client from [setup_mls] are removed).
+/// Number of removed clients is equal to group size (→ all clients except the initial client from [setup_mls] are
+/// removed).
 fn commit_remove_bench(c: &mut Criterion) {
     let mut group = c.benchmark_group("Commit remove f(group size)");
     for (case, ciphersuite, credential, in_memory) in MlsTestCase::values() {

crypto/benches/utils/mls.rs

@@ -153,7 +153,8 @@ pub async fn setup_mls(
 
 pub async fn new_central(
     ciphersuite: Ciphersuite,
-    // TODO: always None for the moment. Need to update the benches with some realistic certificates. Tracking issue: WPB-9589
+    // TODO: always None for the moment. Need to update the benches with some realistic certificates. Tracking issue:
+    // WPB-9589
     _credential: Option<&CertificateBundle>,
     in_memory: bool,
     with_basic_credential: bool,