pub async fn handle_query_changes<O: QueryObject, B: JmapBackend>(
backend: &B,
caller: &B::CallerCtx,
args: Value,
) -> Result<HandlerOutput, JmapError>Expand description
Generic */queryChanges handler (RFC 8620 §5.6).
Parses filter and sort from args, then delegates to
JmapReads::query_changes with collapse_threads: false. For
Email/queryChanges (which may need collapseThreads: true), use the
domain-specific handler in jmap-mail-server instead.
Like handle_get it does not see using, so a non-null language
(draft-atwood-jmap-updates-00 §4.2) is invalidArguments. A type with
JmapObject::LOCALIZABLE properties
uses handle_query_changes_with_i18n or its own handler.
§Errors
Method-level errors, returned as the JmapError:
invalidArgumentsifargsis not an object oraccountIdis missing or not a valid Id. Also whensinceQueryStateis missing,maxChangesis not a positive integer,upToIdis neither a string nornull,filteris not an object,sortis not an array of comparators, orlanguageis non-null.accountNotFoundif the backend reports no such account;serverFail(with a redacted description) if that check fails.unsupportedFilteriffilteris an object that does not decode as the type’s filter.- A
BackendQueryError::Methodfrom the backend unchanged (for examplecannotCalculateChanges); any other backend error becomes the redactedserverFail.