* Add a `feature = "compat"` workaround for Element failing on `GET /_matrix/client/r0/account/3pid` response if the optional `threepids` field is missing -----BEGIN PGP SIGNATURE----- iIwEABYIADQWIQSYRl0lv78dXawPPq7MFU3g4wt8ZwUCYUnGGxYcanBsYXR0ZStn aXRAcG9zdGVvLmRlAAoJEMwVTeDjC3xnXEAA/jR+Jn+XK1TFLY4OhLym8VN+4mxb YLTg0p5mAsyqSXB8AQCXGpCjyYzV1bBFYRx8J2KMTTt0zWwqYRbsCsrUyP2vDQ== =LUOM -----END PGP SIGNATURE----- gpgsig -----BEGIN PGP SIGNATURE----- iIwEABYIADQWIQSYRl0lv78dXawPPq7MFU3g4wt8ZwUCYUnHmxYcanBsYXR0ZStn aXRAcG9zdGVvLmRlAAoJEMwVTeDjC3xnn00A/04e0hPc/cnl5Lzb8Tvy6Xmzc/6W hmRfZdcABHGX0eV7AP4xO/LAeS5qVMfwCo8X0ypPLul+PK9faWgeR0O337ZjAw== =Skqn -----END PGP SIGNATURE----- Merge tag 'ruma-client-api-0.12.3' ruma-client-api 0.12.3 * Add a `feature = "compat"` workaround for Element failing on `GET /_matrix/client/r0/account/3pid` response if the optional `threepids` field is missing
ruma
Types and traits for working with the Matrix protocol.
This crate re-exports things from all of the other ruma crates so you don't have to manually keep all the versions in sync.
Which crates are re-exported can be configured through cargo features. Depending on which parts of Matrix are relevant to you, activate the following features:
client-api
for the client-server APIfederation-api
for the server-server (federation) APIappservice-api
for the application service API