@unispechq/unispec-schema 0.3.6 → 0.3.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/README.md +4 -0
- package/package.json +1 -1
- package/schema/types/websocket.schema.json +4 -0
package/README.md
CHANGED
|
@@ -146,6 +146,10 @@ If omitted, tooling may assume common framework defaults:
|
|
|
146
146
|
- GraphQL: `/graphql`
|
|
147
147
|
- WebSocket: `/ws` (or `/socket.io` for Socket.IO)
|
|
148
148
|
|
|
149
|
+
### WebSocket Namespaces
|
|
150
|
+
|
|
151
|
+
WebSocket channels may include an optional `namespace` field to group related channels and avoid name collisions (e.g. `chat`, `notifications`, `system`).
|
|
152
|
+
|
|
149
153
|
## Examples
|
|
150
154
|
|
|
151
155
|
The examples/ directory contains official UniSpec examples:
|
package/package.json
CHANGED
|
@@ -38,6 +38,10 @@
|
|
|
38
38
|
"description": {
|
|
39
39
|
"$ref": "./common.schema.json#/$defs/Description"
|
|
40
40
|
},
|
|
41
|
+
"namespace": {
|
|
42
|
+
"type": "string",
|
|
43
|
+
"description": "Optional namespace for the channel (e.g. 'chat', 'notifications'). Used to group related channels and avoid name collisions."
|
|
44
|
+
},
|
|
41
45
|
"direction": {
|
|
42
46
|
"type": "string",
|
|
43
47
|
"description": "Direction of message flow on this channel.",
|