@smartytalent/mcp-tools 0.7.6 → 0.7.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/tools.json +27 -11
- package/package.json +1 -1
package/dist/tools.json
CHANGED
|
@@ -22761,21 +22761,37 @@
|
|
|
22761
22761
|
"relationships": {
|
|
22762
22762
|
"title": "NotificationRelationshipsSchema",
|
|
22763
22763
|
"type": "object",
|
|
22764
|
+
"description": "Declared in the WIRE shape, not the storage shape. Rows keep to-many entries as arrays, but transform_all_relationships serialises `users` to-ONE (RELATIONSHIP_TYPES says cardinality one) and renames it `user` - a spec written from the row therefore matches nothing and the generated client silently drops the whole relationship.",
|
|
22764
22765
|
"properties": {
|
|
22765
|
-
"
|
|
22766
|
+
"user": {
|
|
22766
22767
|
"type": "object",
|
|
22768
|
+
"description": "Who the notification is FOR. Singular and to-one on the wire.",
|
|
22767
22769
|
"properties": {
|
|
22768
22770
|
"data": {
|
|
22769
|
-
"type": "
|
|
22770
|
-
"
|
|
22771
|
-
"type":
|
|
22772
|
-
|
|
22773
|
-
|
|
22774
|
-
|
|
22775
|
-
|
|
22776
|
-
|
|
22777
|
-
|
|
22778
|
-
|
|
22771
|
+
"type": "object",
|
|
22772
|
+
"properties": {
|
|
22773
|
+
"type": {
|
|
22774
|
+
"type": "string"
|
|
22775
|
+
},
|
|
22776
|
+
"id": {
|
|
22777
|
+
"type": "string"
|
|
22778
|
+
}
|
|
22779
|
+
}
|
|
22780
|
+
}
|
|
22781
|
+
}
|
|
22782
|
+
},
|
|
22783
|
+
"subject": {
|
|
22784
|
+
"type": "object",
|
|
22785
|
+
"description": "What the notification is ABOUT - the target of the bell's deep link. Always this name, whatever the resource is, and it carries its own `type` so the client routes on that. Producers used to key this by resource type (`tasks`, `jobs`, ...), which cannot be declared here without enumerating every type any producer might ever use, so the typed client dropped all of them; it also collided with `user` outright when the subject was itself a user, overwriting the recipient. Absent when the notification is about nothing in particular.",
|
|
22786
|
+
"properties": {
|
|
22787
|
+
"data": {
|
|
22788
|
+
"type": "object",
|
|
22789
|
+
"properties": {
|
|
22790
|
+
"type": {
|
|
22791
|
+
"type": "string"
|
|
22792
|
+
},
|
|
22793
|
+
"id": {
|
|
22794
|
+
"type": "string"
|
|
22779
22795
|
}
|
|
22780
22796
|
}
|
|
22781
22797
|
}
|