History

Benjamin Lee 3f67772dd3 client-api: Don't skip all no-event timelines serializing sync response

There are some cases where a timeline can have zero events but should
still be included in the api response. For example, when calling `/sync`
with a filter that rejects all events after `since`, but does not
necessarily reject all events in the room's history, the response should
include a `prev_batch` field so that the client can search for earlier
events matching the filter using `/messages`.

2024-05-05 03:09:56 -04:00

src

client-api: Don't skip all no-event timelines serializing sync response

2024-05-05 03:09:56 -04:00

tests

client-api: Move Error authenticate field to ErrorKind::Forbidden

2024-03-31 21:04:18 +02:00

build.rs

ci: Upgrade nightly toolchain

2023-11-08 18:03:26 +01:00

Cargo.toml

client-api: Add unstable support for animated thumbnails

2024-04-27 16:15:21 +02:00

CHANGELOG.md

client-api: Don't skip all no-event timelines serializing sync response

2024-05-05 03:09:56 -04:00

README.md

Move all crates into a new crates directory

2021-05-03 15:50:27 +02:00

README.md

ruma-client-api

ruma-client-api contains serializable types for the requests and responses for each endpoint in the Matrix client API specification. These types can be shared by client and server code.