Struct ruma_client_api::relations::get_relating_events_with_rel_type_and_event_type::v1::IncomingRequest
source · [−]pub struct IncomingRequest {
pub room_id: OwnedRoomId,
pub event_id: OwnedEventId,
pub rel_type: RelationType,
pub event_type: RoomEventType,
pub from: Option<String>,
pub to: Option<String>,
pub limit: Option<UInt>,
}
client
or server
only.Expand description
‘Incoming’ variant of Request.
Fields
room_id: OwnedRoomId
The ID of the room containing the parent event.
event_id: OwnedEventId
The ID of the parent event whose child events are to be returned.
rel_type: RelationType
The relationship type to search for.
event_type: RoomEventType
The event type of child events to search for.
Note that in encrypted rooms this will typically always be m.room.encrypted
regardless of the event type contained within the encrypted payload.
from: Option<String>
The pagination token to start returning results from.
If None
, results start at the most recent topological event known to the server.
Can be a next_batch
token from a previous call, or a returned start
token from
/messages
or a next_batch
token from /sync
.
Note that when paginating the from
token should be “after” the to
token in
terms of topological ordering, because it is only possible to paginate “backwards”
through events, starting at from
.
to: Option<String>
The pagination token to stop returning results at.
If None
, results continue up to limit
or until there are no more events.
Like from
, this can be a previous token from a prior call to this endpoint
or from /messages
or /sync
.
limit: Option<UInt>
The maximum number of results to return in a single chunk
.
The server can and should apply a maximum value to this parameter to avoid large responses.
Similarly, the server should apply a default value when not supplied.
Trait Implementations
sourceimpl Debug for IncomingRequest
impl Debug for IncomingRequest
sourceimpl IncomingRequest for IncomingRequest
Available on crate feature server
only.
impl IncomingRequest for IncomingRequest
server
only.