Skip to content

Commit d6a2e5c

Browse files
committed
chore: add missing $def to files
1 parent f62a4e4 commit d6a2e5c

File tree

21 files changed

+153
-134
lines changed

21 files changed

+153
-134
lines changed

packages/live-status-gateway-api/api/refactor/components/adLibs/bucketAdLib/bucketAdLib.yaml

Lines changed: 0 additions & 13 deletions
This file was deleted.

packages/live-status-gateway-api/api/refactor/components/adLibs/bucketAdLib/bucketAdLib-example.yaml renamed to packages/live-status-gateway-api/api/refactor/components/adLibs/bucketAdLibStatus/bucketAdLibStatus-example.yaml

File renamed without changes.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
$defs:
2+
bucketAdLibStatus:
3+
title: BucketAdLibStatus
4+
allOf:
5+
- $ref: '../adLibBase/adLibBase.yaml#/$defs/adLibBase'
6+
- type: object
7+
title: BucketAdLibStatus
8+
properties:
9+
externalId:
10+
type: string
11+
description: Id of the adlib recognizable by the external source. Unique within a bucket.
12+
required: [externalId]
13+
examples:
14+
- $ref: './bucketAdLibStatus-example.yaml'
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
id: 'C6K_yIMuGFUk8X_L9A9_jRT6aq4_'
22
name: My Bucket
33
adLibs:
4-
- $ref: '../../adLibs/bucketAdLib/bucketAdLib-example.yaml'
4+
- $ref: '../../adLibs/bucketAdLibStatus/bucketAdLibStatus-example.yaml'

packages/live-status-gateway-api/api/refactor/components/buckets/bucketStatus/bucketStatus.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ $defs:
1313
description: The AdLibs in this bucket
1414
type: array
1515
items:
16-
$ref: '../../adLibs/bucketAdlib/bucketAdLib.yaml'
16+
$ref: '../../adLibs/bucketAdlibStatus/bucketAdLibStatus.yaml#/$defs/bucketAdLibStatus'
1717
required: [id, name, adLibs]
1818
additionalProperties: false
1919
examples:
Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
1-
title: HeartbeatEvent
2-
type: object
3-
properties:
4-
event:
5-
type: string
6-
const: heartbeat
7-
required: [event]
8-
additionalProperties: false
9-
examples:
10-
- $ref: './heartbeatEvent-example.yaml'
1+
$defs:
2+
heartbeatEvent:
3+
title: HeartbeatEvent
4+
type: object
5+
properties:
6+
event:
7+
type: string
8+
const: heartbeat
9+
required: [event]
10+
additionalProperties: false
11+
examples:
12+
- $ref: './heartbeatEvent-example.yaml'

packages/live-status-gateway-api/api/refactor/components/connection/messages/heartbeatMessage.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ components:
55
messageId: heartbeat
66
description: Server heartbeat sent if no subscription traffic within 1 second (approximately)
77
payload:
8-
$ref: '../heartbeatEvent/heartbeatEvent.yaml'
8+
$ref: '../heartbeatEvent/heartbeatEvent.yaml#/$defs/heartbeatEvent'
99
examples:
1010
- payload:
1111
$ref: '../heartbeatEvent/heartbeatEvent-example.yaml'

packages/live-status-gateway-api/api/refactor/components/connection/messages/pingMessage.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ components:
66
summary: Ping server to determine whether connection is alive
77
description: Client can ping server to determine whether connection is alive, server responds with pong. This is an application level ping as opposed to default ping in websockets standard which is server initiated
88
payload:
9-
$ref: '../pingEvent/pingEvent.yaml'
9+
$ref: '../pingEvent/pingEvent.yaml#/$defs/pingEvent'
1010
examples:
1111
- payload:
1212
$ref: '../pingEvent/pingEvent-example.yaml'

packages/live-status-gateway-api/api/refactor/components/connection/messages/pongMessage.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ components:
66
summary: Pong is a response to ping message
77
description: Server pong response to a ping to determine whether connection is alive. This is an application level pong as opposed to default pong in websockets standard which is sent by client in response to a ping
88
payload:
9-
$ref: '../pongEvent/pongEvent.yaml'
9+
$ref: '../pongEvent/pongEvent.yaml#/$defs/pongEvent'
1010
examples:
1111
- payload:
1212
$ref: '../pongEvent/pongEvent-example.yaml'
Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
1-
title: PingEvent
2-
type: object
3-
properties:
4-
event:
5-
type: string
6-
const: ping
7-
reqid:
8-
$ref: '../reqid/reqid.yaml'
9-
required: [event, reqid]
10-
additionalProperties: false
11-
examples:
12-
- $ref: './pingEvent-example.yaml'
1+
$defs:
2+
pingEvent:
3+
title: PingEvent
4+
type: object
5+
properties:
6+
event:
7+
type: string
8+
const: ping
9+
reqid:
10+
$ref: '../reqid/reqid.yaml#/$defs/reqid'
11+
required: [event, reqid]
12+
additionalProperties: false
13+
examples:
14+
- $ref: './pingEvent-example.yaml'

0 commit comments

Comments
 (0)