site.exosphere.kanban.status
Schema Diff
+13 -1
Compatibility Analysis
Backward Compatible
Backward compatible. 2 non-breaking changes.
Non-Breaking Changes (2)
- AddedVertex AddedVertex { vertex_id: "site.exosphere.kanban.status:body.statusType" }
- AddedEdge AddedEdge { src: "site.exosphere.kanban.status:body", tgt: "site.exosphere.kanban.status:body.statusType", kind: "prop", name: Some("statusType") }
Migration Guidance
Added Elements
AddedVertex { vertex_id: "site.exosphere.kanban.status:body.statusType" }
Additional Notes
- Non-breaking: AddedEdge { src: "site.exosphere.kanban.status:body", tgt: "site.exosphere.kanban.status:body.statusType", kind: "prop", name: Some("statusType") }
1
1
{
2
2
"id": "site.exosphere.kanban.status",
3
3
"defs": {
4
4
"main": {
5
5
"key": "tid",
6
6
"type": "record",
7
7
"record": {
8
8
"type": "object",
9
9
"required": [
10
10
"subject",
11
-
"status"
11
+
"status",
12
+
"statusType"
12
13
],
13
14
"properties": {
14
15
"status": {
15
16
"type": "string",
16
17
"maxLength": 128,
17
18
"description": "Column slug the task is moved to. Values are user-defined per Sphere.",
18
19
"knownValues": [
19
20
"backlog",
20
21
"todo",
21
22
"in-progress",
22
23
"done"
23
24
]
24
25
},
25
26
"subject": {
26
27
"type": "string",
27
28
"format": "at-uri",
28
29
"description": "AT URI of the kanban task whose status is being changed."
30
+
},
31
+
"statusType": {
32
+
"type": "string",
33
+
"description": "Canonical status type the column maps to. Third-party indexers use this to categorize user-defined slugs without needing the sphere's column config.",
34
+
"knownValues": [
35
+
"backlog",
36
+
"planned",
37
+
"started",
38
+
"completed",
39
+
"canceled"
40
+
]
29
41
}
30
42
}
31
43
},
32
44
"description": "A status change on a kanban task, published on the actor's PDS. Third-party indexers can replay these to derive the current column of a task."
33
45
}
34
46
},
35
47
"$type": "com.atproto.lexicon.schema",
36
48
"lexicon": 1
37
49
}