Skip to main content

Module task_notification

Module task_notification 

Source
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/changes method call (draft-tasks-06 §5.3).
handle_task_notification_get
Handle a TaskNotification/get method call (draft-tasks-06 §5.2).
handle_task_notification_query
Handle a TaskNotification/query method call (draft-tasks-06 §5.5).
handle_task_notification_query_changes
Handle a TaskNotification/queryChanges method call (draft-tasks-06 §5.6).
handle_task_notification_set
Handle a TaskNotification/set method call (draft-tasks-06 §5.4).