mirror of https://github.com/logos-messaging/libchat.git synced 2026-06-27 19:49:31 +00:00

History

osmaczko addcde03eb feat: introduce client event system

- Core returns `InboundResult` — a typed struct with an optional
  `NewConversation` and a `FrameOutcome` of decrypted messages.
- Client surfaces app-facing events via `Vec<Event>`, translated from
  `InboundResult` at the boundary.
- MLS group welcomes now produce a `ConversationStarted` event with no
  initial content, fixing the silent-group-join case where the inbox
  layer dropped the observation.
- C FFI exposes an `EventList` opaque type with indexed accessors and
  an `Invalid` sentinel for OOB / non-applicable reads.
- Symmetric `Inbox` / `InboxV2` handlers: both return
  `Result<InboundResult, _>` and own the persistence + ephemeral-key
  cleanup for the conversations they create.
- Updated and simplified `docs/adr/0001-client-event-system.md`.

2026-05-26 12:05:44 +02:00

main.rs

feat: introduce client event system

2026-05-26 12:05:44 +02:00

README.md

feat: implement Client crate and C FFI bindings (#73 )

2026-04-08 23:15:48 +02:00

README.md

message-exchange

An example Rust application built on top of crates/client.

It demonstrates that creating a working chat client in pure Rust is trivial: depend on crates/client, pick a DeliveryService implementation (here the in-memory InProcessDelivery shipped with the crate), and wire up ChatClient. No boilerplate, no FFI.

Running

cargo run --example message-exchange

The binary performs a message exchange entirely in-process and prints the exchanged messages to stdout.