chris/ruwuma
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

client-api: Add timestamp onto SlidingSyncRoom

Browse Source 
This has been added in
https://github.com/matrix-org/sliding-sync/pull/247. This is not part of
the MSC yet.
This commit is contained in:
Ivan Enderlin 2023-08-17 11:52:00 +02:00 committed by GitHub
parent 6fcd813201
commit a9a6e67ed0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
crates/ruma-client-api/src/sync/sync_events/v4.rs
View File

@ -17,7 +17,7 @@ use ruma_common::{
}, },
metadata, metadata,
serde::{duration::opt_ms, Raw}, serde::{duration::opt_ms, Raw},
DeviceKeyAlgorithm, OwnedMxcUri, OwnedRoomId, DeviceKeyAlgorithm, MilliSecondsSinceUnixEpoch, OwnedMxcUri, OwnedRoomId,
}; };
use serde::{Deserialize, Serialize}; use serde::{Deserialize, Serialize};
@ -468,6 +468,15 @@ pub struct SlidingSyncRoom {
/// The number of timeline events which have just occurred and are not historical. /// The number of timeline events which have just occurred and are not historical.
#[serde(skip_serializing_if = "Option::is_none")] #[serde(skip_serializing_if = "Option::is_none")]
pub num_live: Option<UInt>, pub num_live: Option<UInt>,
/// The timestamp of the room.
///
/// It's not to be confused with `origin_server_ts` of the latest event in the
/// timeline. `bump_event_types` might "ignore” some events when computing the
/// timestamp of the room. Thus, using this `timestamp` value is more accurate than
/// relying on the latest event.
#[serde(skip_serializing_if = "Option::is_none")]
pub timestamp: Option<MilliSecondsSinceUnixEpoch>,
} }
impl SlidingSyncRoom { impl SlidingSyncRoom {