libchat/crates/client/src/errors.rs

use libchat::ChatError;

#[derive(Debug, thiserror::Error)]
pub enum ClientError<D: std::fmt::Display> {
    #[error(transparent)]
    Chat(#[from] ChatError),
    /// Crypto state advanced but at least one envelope failed delivery.
    /// Caller decides whether to retry.
    #[error("delivery failed: {0:?}")]
    Delivery(D),
}
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00			`use libchat::ChatError;`

			`#[derive(Debug, thiserror::Error)]`
Add GroupV1 + InboxV2 (#92) * Add GroupV1 * Clean warnings * Remove dead test * Re-use components in integration tests * Remove deadcode * undo import fixes * tidy * Update Accounts + service_traits * Remove ClientCtx * Remove duplicate test_utils * Wrap constructor in result * Warning fixups * Appease clippy * Update comments * Update todo * Clean up warnings * Avoid panic * Fix libchat import in chat-cli * Add InboxV2 comment * Add comments to GroupV1Convo * Update doc comments * reduce visibility * Doc Integration tests * Hashlen update * remove type alias for ProtocolParams * Remove stray printlines * Review fixes * PR review changes * Add trait comments * chat_proto import paths * PR Feedback fixes * Update CliClient * Update CLI DeliveryService impls 2026-05-19 11:54:54 -07:00			`pub enum ClientError<D: std::fmt::Display> {`
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00			`#[error(transparent)]`
			`Chat(#[from] ChatError),`
			`/// Crypto state advanced but at least one envelope failed delivery.`
			`/// Caller decides whether to retry.`
			`#[error("delivery failed: {0:?}")]`
			`Delivery(D),`
			`}`