mirror of
https://github.com/matrix-org/matrix-rust-sdk.git
synced 2026-05-06 15:04:11 -04:00
e00d57fee2
The test ends up with checking that the redact endpoint has been hit once. It's actually the send queue doing the redaction as a dependent send request, and it doesn't provide any notification mechanism in this case, so we can't really know when it's done doing it. One solution would be to not check the number of calls to the redact/ endpoint, but that means checking for fewer things. Instead, I made it so that when hit, the endpoint will signal it to the main task using a oneshot channel; then the main task waits with a long timeout for the receiving end to get the notification it's been sent, which should be sufficient.
matrix-rust-sdk
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust.
Project structure
The rust-sdk consists of multiple crates that can be picked at your convenience:
- matrix-sdk - High level client library, with batteries included, you're most likely interested in this.
- matrix-sdk-base - No (network) IO client state machine that can be used to embed a Matrix client in your project or build a full fledged network enabled client lib on top of it.
- matrix-sdk-crypto - No (network) IO encryption state machine that can be used to add Matrix E2EE support to your client or client library.
Status
The library is considered production ready and backs multiple client implementations such as Element X [1] [2] and Fractal. Client developers should feel confident to build upon it.
Development of the SDK has been primarily sponsored by Element though accepts contributions from all.
Bindings
Some crates of the matrix-rust-sdk can be embedded inside other
environments, like Swift, Kotlin, JavaScript, Node.js etc. Please,
explore the bindings/ directory to learn more.