app.didpic.notification.registerPush
Schema Diff
+11 -5
Compatibility Analysis
Backward Compatible
Backward compatible. 2 non-breaking changes.
Non-Breaking Changes (2)
- AddedVertex AddedVertex { vertex_id: "app.didpic.notification.registerPush:input.kind" }
- AddedEdge AddedEdge { src: "app.didpic.notification.registerPush:input", tgt: "app.didpic.notification.registerPush:input.kind", kind: "prop", name: Some("kind") }
Migration Guidance
Added Elements
AddedVertex { vertex_id: "app.didpic.notification.registerPush:input.kind" }
Additional Notes
- Non-breaking: AddedEdge { src: "app.didpic.notification.registerPush:input", tgt: "app.didpic.notification.registerPush:input.kind", kind: "prop", name: Some("kind") }
1
1
{
2
2
"id": "app.didpic.notification.registerPush",
3
3
"defs": {
4
4
"main": {
5
5
"type": "procedure",
6
6
"input": {
7
7
"schema": {
8
8
"type": "object",
9
9
"required": [
10
10
"token",
11
11
"platform"
12
12
],
13
13
"properties": {
14
+
"kind": {
15
+
"type": "string",
16
+
"knownValues": [
17
+
"expo",
18
+
"apns",
19
+
"fcm"
20
+
]
21
+
},
14
22
"token": {
15
-
"type": "string",
16
-
"description": "Expo push token of the form `ExponentPushToken[...]`."
23
+
"type": "string"
17
24
},
18
25
"platform": {
19
26
"type": "string",
20
27
"knownValues": [
21
28
"ios",
22
29
"android"
23
30
]
24
31
},
25
32
"accountsOnDevice": {
26
33
"type": "array",
27
34
"items": {
28
35
"type": "string",
29
36
"format": "did"
30
-
},
31
-
"description": "DIDs the calling device currently has signed in. When provided, the server replaces all (token, *) bindings to match this list: bindings for DIDs absent from it are pruned. Must include the authenticated DID. Lets a multi-account device reconcile after an account is removed without needing the gone account's auth."
37
+
}
32
38
}
33
39
}
34
40
},
35
41
"encoding": "application/json"
36
42
},
37
-
"description": "Bind a device's push token to the authenticated viewer. Idempotent: re-registering the same (token, did) pair refreshes its registered_at. A single token can be bound to multiple DIDs (multi-account device); a single DID can be bound to multiple tokens (multiple devices for one account)."
43
+
"description": "Bind a device push token to the authenticated viewer."
38
44
}
39
45
},
40
46
"$type": "com.atproto.lexicon.schema",
41
47
"lexicon": 1
42
48
}