-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Rust SDK to latest version #134
Conversation
Fixes #132 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update the changelog pls?
src/encryption.rs
Outdated
/// Strategy to collect the devices that should receive room keys for the | ||
/// current discussion. | ||
/// | ||
/// See matrix_sdk_crypto::CollectStrategy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make these docs stand in their own right, so that the online doc (https://matrix-org.github.io/matrix-rust-sdk-crypto-wasm/classes/OlmMachine.html) is useful. (The fact that there are existing docs that just point to a Rust class is definitely bad.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
src/encryption.rs
Outdated
#[wasm_bindgen()] | ||
#[derive(Debug, Clone, PartialEq, Eq)] | ||
/// Strategy to collect the devices that should receive room keys for the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put the #[…]
after the documentation. It's more Rust idiomatic to do so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
I've added a changelog. I'm not sure what the criteria are for which rust-sdk-crypto changes to highlight in the changelogs, so I just highlighted the one that causes the breaking change. |
Looks like three different matrix-rust-sdk PRs introduced incompatible changes. This is my attempt to fix them. I'm certain that the fix for my PR is correct, but fairly sure that the
sender_data
fix is correct, and less sure that theCollectStrategy
fix is sensible.This introduces a change that will break js-sdk (yay for cascading breakage), so that will need to be updated.
Not sure why the test is failing. Seems to be unrelated to the changes here, so must be some change elsewhere. I'm guessing that it should be fine to update the expected values to the actual values, but someone who knows about why the discrepancy is there should verify.