#[non_exhaustive]pub struct SessionListResult {
pub sessions: Vec<Session>,
pub next_cursor: Option<String>,
pub applied_filter: Option<SessionListFilter>,
}Expand description
session/list result. The default order is content activity:
lastActivityAt descending, then sessionId ascending. The order is the
session index’s key, so a row’s displayed timestamps do not always show its
position: a row the index has not yet derived keeps its updatedAt
position, a derived row with no content orders by createdAt, and a loaded
row can show newer values. Do not re-sort or validate a page from them.
updatedAfter still filters on updatedAt.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.sessions: Vec<Session>The page of stored sessions.
next_cursor: Option<String>The next page’s cursor; null on the last page.
applied_filter: Option<SessionListFilter>The canonical filter the server applied, present exactly when the
request carried filter. The probe is per-predicate PRESENCE: a client
that requires filtering checks that every predicate it sent comes back
as a member here, and treats a missing member as unsupported. Value
equality is the wrong test — canonicalization trims, lowercases,
NFC-normalizes, dedupes and sorts, so the echoed values often differ
from the sent ones on a correctly filtered page.