1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
//! TasksBackend trait and supporting types for JMAP Tasks method handlers.
//!
//! Consumers implement [`TasksBackend`] for their storage system. The method
//! handlers in sibling modules call into the backend through this trait.
//!
//! The read-side operations (`get_objects`, `get_state`, `get_changes`,
//! `query_objects`, `query_changes`) are defined on the [`jmap_server::JmapBackend`]
//! supertrait. Only write operations and type-specific operations are here.
// ── Re-exports from jmap-server (the foundation crate) ────────────────────
//
// Every TasksBackend implementor needs these names. They are re-exported
// here so a consumer can write `use jmap_tasks_server::backend::*;` and get
// the full vocabulary in one import.
/// JMAP wire-format SetError; emitted by [`TasksBackend`] write methods
/// wrapped as [`BackendSetError::SetError`] and serialised into
/// `notCreated` / `notUpdated` / `notDestroyed` maps by the `/set` handlers
/// (RFC 8620 §5.3).
pub use SetError;
/// The standard wire-format SetError type tag (RFC 8620 §5.3 +
/// extension-specific types like `taskListHasTask` from
/// draft-ietf-jmap-tasks-06 §3.4).
pub use SetErrorType;
/// Backend-side wrapper around [`SetError`]; the trait's write methods
/// return `Result<…, BackendSetError<Self::Error>>`. The handler unwraps
/// `BackendSetError::SetError` into the per-target SetError map and
/// folds `BackendSetError::Other(e)` into a top-level `serverFail`.
pub use BackendSetError;
/// Backend-side error wrapper for `/changes` paths (RFC 8620 §5.2);
/// distinguished from [`BackendSetError`] because the `cannotCalculateChanges`
/// recovery is a `/changes`-specific contract.
pub use BackendChangesError;
/// Result of [`JmapBackend::get_changes`] (RFC 8620 §5.2). Carries
/// `created`, `updated`, `destroyed`, the `hasMoreChanges` flag, and the
/// new state token.
pub use ChangesResult;
/// Result of [`JmapBackend::query_objects`] (RFC 8620 §5.5). Carries the
/// id list, anchor position, total count (when requested), and state.
pub use QueryResult;
/// Result of [`JmapBackend::query_changes`] (RFC 8620 §5.6). Carries
/// `added`, `removed`, optional total count, and the new state.
pub use QueryChangesResult;
/// One entry in the `added` array of a [`QueryChangesResult`]: a typed
/// `(index, id)` pair.
pub use AddedItem;
/// Foundation `JmapBackend` supertrait. [`TasksBackend`] extends this with
/// Task-specific methods; consumers must implement both.
pub use JmapBackend;
/// Marker trait identifying a JMAP object type (RFC 8620 §5). Used as a
/// bound on `get_state` / `get_changes` / `query_objects`.
pub use JmapObject;
/// Marker trait identifying a "gettable" JMAP object type. Adds the
/// property-projection contract on top of [`JmapObject`].
pub use GetObject;
/// Marker trait identifying a "settable" JMAP object type. Adds the
/// `Patch` associated type on top of [`JmapObject`].
pub use SetObject;
/// Marker trait identifying a "queryable" JMAP object type. Adds the
/// `Filter` and `Comparator` associated types on top of [`JmapObject`].
pub use QueryObject;
// ── Property selector enums from jmap-tasks-types ────────────────────────
//
// These let backends interpret the `properties` argument on /get without
// reparsing string literals.
/// `TaskList` property selector enum (draft-ietf-jmap-tasks-06 §3); used
/// in [`JmapBackend::get_objects::<TaskList>`] property projection.
pub use TaskListProperty;
/// `Task` property selector enum (draft-ietf-jmap-tasks-06 §4); used in
/// [`JmapBackend::get_objects::<Task>`] property projection.
pub use TaskProperty;
/// `TaskNotification` property selector enum
/// (draft-ietf-jmap-tasks-06 §5).
pub use TaskNotificationProperty;
// ── Wire types from jmap-types ───────────────────────────────────────────
/// JMAP wire-format `PatchObject` (RFC 8620 §5.3) — a JSON-Pointer-keyed
/// map of property paths to new values, used as the patch payload for
/// `update_object` and `update_task_per_user`.
pub use PatchObject;
// ---------------------------------------------------------------------------
// TasksBackend trait
// ---------------------------------------------------------------------------
/// Storage backend for JMAP Tasks method handlers (draft-ietf-jmap-tasks-06).
///
/// Implementors provide the actual data access; the method handler modules
/// in this crate translate between JMAP wire protocol and backend calls.
///
/// Read-side operations (`get_objects`, `get_state`, `get_changes`,
/// `query_objects`, `query_changes`) are defined on the [`JmapBackend`]
/// supertrait. Only write operations and type introspection are here.
///
/// This trait is not object-safe by design (generic methods). Use
/// `Arc<impl TasksBackend>` when sharing across tasks.