pub async fn handle_message_query_changes<B: ChatBackend>(
backend: &B,
caller: &B::CallerCtx,
args: Value,
using: &[String],
) -> Result<HandlerOutput, JmapError>Expand description
Handle a Message/queryChanges method call (draft-atwood-jmap-chat-00 §Message).
args is the RFC 8620 §5.6 /queryChanges request shape (accountId,
optional filter, optional sort, sinceQueryState, optional
maxChanges, optional upToId, optional calculateTotal); the
returned Value is the §5.6 /queryChanges response shape
(accountId, oldQueryState, newQueryState, optional total,
removed, added).
A query scoped to one Chat the caller cannot view fails with
cannotCalculateChanges, so the client re-runs Message/query, which
returns nothing for that Chat (see handle_message_query).
using is the request’s capability list (pass
jmap_server::CallContext::using); without
urn:ietf:params:jmap:metadata a draft-ietf-jmap-metadata-04 §3.6
filter condition is unsupportedFilter (-04 §3).
Returns (response_args, extra_invocations). The extra list is always empty.