Expand description
TaskNotification/* method handlers (draft-tasks-06 §5).
TaskNotifications are server-created immutable records. Clients may only
query and destroy them. Any attempt to create or update a TaskNotification
via /set MUST be rejected with forbidden at the handler layer — the
backend never sees create or update calls for this type.
§Wire-shape contract
Every handle_* function in this module conforms to the canonical JMAP
method shape. The args: serde_json::Value parameter MUST be a JSON
Object whose fields match the corresponding RFC 8620 §5 method shape
(/get → §5.1, /changes → §5.2, /set → §5.3,
/query → §5.5, /queryChanges → §5.6), with the type-specific
arguments defined by draft-tasks-06 §5. The returned Value is the
corresponding method-response object per the same section refs.
The returned Vec<Invocation> carries any back-reference invocations
that this handler injected into the request stream (RFC 8620 §6.3);
for the handlers in this module the vector is always empty.
Each handler returns Err(JmapError) for method-level failures
(accountNotFound, invalidArguments, stateMismatch, serverFail,
unsupportedFilter, unsupportedSort, cannotCalculateChanges —
per RFC 8620 §3.6 and §5). Per-target failures inside /set surface
in the notDestroyed map within Ok((Value, ...)), not as Err.
Functions§
- handle_
task_ notification_ changes - Handle a
TaskNotification/changesmethod call (draft-tasks-06 §5.3). - handle_
task_ notification_ get - Handle a
TaskNotification/getmethod call (draft-tasks-06 §5.2). - handle_
task_ notification_ query - Handle a
TaskNotification/querymethod call (draft-tasks-06 §5.5). - handle_
task_ notification_ query_ changes - Handle a
TaskNotification/queryChangesmethod call (draft-tasks-06 §5.6). - handle_
task_ notification_ set - Handle a
TaskNotification/setmethod call (draft-tasks-06 §5.4).