03e53e991b
Also refactor and document why this hoisting is needed. This change makes the user_presence test fail because the hoisting exposes an error encoded into the test's expected result. Previously, the test expected 2 members in the room at the end. This is incorrect since one of the members in the test data leaves the room. However, since the prev_content of state events was previously not hoisted to the top level, the `membership_change` method would not notice it and thus not realize the member had left the room. The test was corrected to expect only a single member in the room. Another test change was made due to a limitation of EventBuilder: due to the fact that it makes the test data go through a de/ser cycle, it cannot easily hoist prev_content to the top level. Because of this, the tests were change to put prev_content into the top level from the outset. |
||
---|---|---|
matrix_sdk | ||
matrix_sdk_base | ||
matrix_sdk_common | ||
matrix_sdk_crypto | ||
matrix_sdk_test | ||
matrix_sdk_test_macros | ||
test_data | ||
.gitignore | ||
.pre-commit-config.yaml | ||
.travis.yml | ||
Cargo.toml | ||
LICENSE | ||
Makefile | ||
README.md | ||
design.md |
README.md
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 in an alpha state, things that are implemented generally work but the API will change in breaking ways.
If you are interested in using the matrix-sdk now is the time to try it out and provide feedback.