Struct CryptoSyncHandler 

pub struct CryptoSyncHandler {
    client: Client,
}

[bitwarden_sync::SyncHandler] implementation of the same work, reading the key id straight off the generated sync response model.

Unused while the clients still own sync — they call CryptoSyncHandlerClient::on_sync instead — but this is the entry point that survives once sync moves into the SDK.

Not available on wasm32: [bitwarden_sync::SyncHandler] requires Send futures, while the generated bitwarden-api-api client is ?Send on that target. bitwarden-sync is not exposed to the wasm bindings either, so nothing is lost — wasm callers use CryptoSyncHandlerClient::on_sync.

Fields

client: Client

Implementations

impl CryptoSyncHandler

pub fn new(client: Client) -> Self

Creates a handler bound to the given client.

Trait Implementations

impl SyncHandler for CryptoSyncHandler

fn on_sync<'life0, 'life1, 'async_trait>( &'life0 self, response: &'life1 SyncResponseModel, ) -> Pin<Box<dyn Future<Output = Result<(), SyncHandlerError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

Called after a successful sync operation

fn on_sync_complete<'life0, 'async_trait>( &'life0 self, ) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>>

where 'life0: 'async_trait, Self: 'async_trait,

Called after all handlers have finished processing on_sync