libchat/crates/client/Cargo.toml

[package]
name = "client"
version = "0.1.0"
edition = "2024"

[lib]
crate-type = ["rlib"]

[dependencies]
# Workspace dependencies (sorted)
chat-sqlite = { workspace = true }
components = { workspace = true } 
libchat = { workspace = true }
logos-account = { workspace = true, features = ["dev"] }

# External dependencies (sorted)
thiserror = "2"

[dev-dependencies]
# External dependencies (sorted)
tempfile = "3"
Flatten Repos (#70) * move to “crates” style folder * Update workspace * clear crate names * Rename crate folders based on feedback * Use workspace dependencies instead of paths * Move updated files from core 2026-03-24 18:21:00 -07:00			`[package]`
			`name = "client"`
			`version = "0.1.0"`
			`edition = "2024"`

			`[lib]`
			`crate-type = ["rlib"]`

			`[dependencies]`
Sort all Cargo.toml deps for less conflicts 2026-05-01 12:24:47 -07:00			`# Workspace dependencies (sorted)`
Move relative path deps to workspace 2026-05-01 13:25:35 -07:00			`chat-sqlite = { workspace = true }`
Make conversations generic over IdentityProvider 2026-05-02 09:39:48 -07:00			`components = { workspace = true }`
Flatten Repos (#70) * move to “crates” style folder * Update workspace * clear crate names * Rename crate folders based on feedback * Use workspace dependencies instead of paths * Move updated files from core 2026-03-24 18:21:00 -07:00			`libchat = { workspace = true }`
Make conversations generic over IdentityProvider 2026-05-02 09:39:48 -07:00			`logos-account = { workspace = true, features = ["dev"] }`
Sort all Cargo.toml deps for less conflicts 2026-05-01 12:24:47 -07:00
			`# External dependencies (sorted)`
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			`thiserror = "2"`

			`[dev-dependencies]`
Sort all Cargo.toml deps for less conflicts 2026-05-01 12:24:47 -07:00			`# External dependencies (sorted)`
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			`tempfile = "3"`