@iveri/contracts 0.29.0 → 0.30.0
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/cjs/api/realtime/realtime-event-type.enum.d.ts +15 -1
- package/dist/cjs/api/realtime/realtime-event-type.enum.d.ts.map +1 -1
- package/dist/cjs/api/realtime/realtime-event-type.enum.js +14 -0
- package/dist/cjs/api/realtime/realtime-event-type.enum.js.map +1 -1
- package/dist/esm/api/realtime/realtime-event-type.enum.d.ts +15 -1
- package/dist/esm/api/realtime/realtime-event-type.enum.d.ts.map +1 -1
- package/dist/esm/api/realtime/realtime-event-type.enum.js +14 -0
- package/dist/esm/api/realtime/realtime-event-type.enum.js.map +1 -1
- package/package.json +1 -1
|
@@ -10,6 +10,20 @@ export declare enum RealtimeEventType {
|
|
|
10
10
|
DELIVERY_JOB_UPDATED = "delivery.job.updated",
|
|
11
11
|
MOBILITY_WORKER_UPDATED = "mobility.worker.updated",
|
|
12
12
|
MOBILITY_WORKER_LOCATION_UPDATED = "mobility.worker-location.updated",
|
|
13
|
-
MOBILITY_ASSIGNMENT_UPDATED = "mobility.assignment.updated"
|
|
13
|
+
MOBILITY_ASSIGNMENT_UPDATED = "mobility.assignment.updated",
|
|
14
|
+
/**
|
|
15
|
+
* An offer addressed to a worker changed, so their own offer list is stale.
|
|
16
|
+
*
|
|
17
|
+
* Carried on the **`mobility.worker` resource**, not an offer resource, and that is the whole
|
|
18
|
+
* point: a worker cannot subscribe to an offer that does not exist yet, and discovering new
|
|
19
|
+
* work is exactly the case realtime has to serve. They subscribe to themselves — the one
|
|
20
|
+
* identifier they hold before any offer is made — and refetch their self-scoped offer list.
|
|
21
|
+
*
|
|
22
|
+
* The event therefore names one resource while describing another aggregate, so its version
|
|
23
|
+
* must be the **offer's**, never the worker's. Publishing the worker's version here would
|
|
24
|
+
* repeat a value the profile events already used and be silently discarded by the outbox's
|
|
25
|
+
* uniqueness constraint. `mobility_worker_outbox_event.aggregate_type` exists for this.
|
|
26
|
+
*/
|
|
27
|
+
MOBILITY_DISPATCH_OFFER_UPDATED = "mobility.dispatch-offer.updated"
|
|
14
28
|
}
|
|
15
29
|
//# sourceMappingURL=realtime-event-type.enum.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"realtime-event-type.enum.d.ts","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,oBAAY,iBAAiB;IACzB,iBAAiB,sBAAsB;IACvC,oBAAoB,yBAAyB;IAC7C,uBAAuB,4BAA4B;IACnD,gCAAgC,qCAAqC;IACrE,2BAA2B,gCAAgC;
|
|
1
|
+
{"version":3,"file":"realtime-event-type.enum.d.ts","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,oBAAY,iBAAiB;IACzB,iBAAiB,sBAAsB;IACvC,oBAAoB,yBAAyB;IAC7C,uBAAuB,4BAA4B;IACnD,gCAAgC,qCAAqC;IACrE,2BAA2B,gCAAgC;IAE3D;;;;;;;;;;;;OAYG;IACH,+BAA+B,oCAAoC;CACtE"}
|
|
@@ -15,5 +15,19 @@ var RealtimeEventType;
|
|
|
15
15
|
RealtimeEventType["MOBILITY_WORKER_UPDATED"] = "mobility.worker.updated";
|
|
16
16
|
RealtimeEventType["MOBILITY_WORKER_LOCATION_UPDATED"] = "mobility.worker-location.updated";
|
|
17
17
|
RealtimeEventType["MOBILITY_ASSIGNMENT_UPDATED"] = "mobility.assignment.updated";
|
|
18
|
+
/**
|
|
19
|
+
* An offer addressed to a worker changed, so their own offer list is stale.
|
|
20
|
+
*
|
|
21
|
+
* Carried on the **`mobility.worker` resource**, not an offer resource, and that is the whole
|
|
22
|
+
* point: a worker cannot subscribe to an offer that does not exist yet, and discovering new
|
|
23
|
+
* work is exactly the case realtime has to serve. They subscribe to themselves — the one
|
|
24
|
+
* identifier they hold before any offer is made — and refetch their self-scoped offer list.
|
|
25
|
+
*
|
|
26
|
+
* The event therefore names one resource while describing another aggregate, so its version
|
|
27
|
+
* must be the **offer's**, never the worker's. Publishing the worker's version here would
|
|
28
|
+
* repeat a value the profile events already used and be silently discarded by the outbox's
|
|
29
|
+
* uniqueness constraint. `mobility_worker_outbox_event.aggregate_type` exists for this.
|
|
30
|
+
*/
|
|
31
|
+
RealtimeEventType["MOBILITY_DISPATCH_OFFER_UPDATED"] = "mobility.dispatch-offer.updated";
|
|
18
32
|
})(RealtimeEventType || (exports.RealtimeEventType = RealtimeEventType = {}));
|
|
19
33
|
//# sourceMappingURL=realtime-event-type.enum.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"realtime-event-type.enum.js","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":";;;AAAA;;;;;;GAMG;AACH,IAAY,
|
|
1
|
+
{"version":3,"file":"realtime-event-type.enum.js","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":";;;AAAA;;;;;;GAMG;AACH,IAAY,iBAqBX;AArBD,WAAY,iBAAiB;IACzB,4DAAuC,CAAA;IACvC,kEAA6C,CAAA;IAC7C,wEAAmD,CAAA;IACnD,0FAAqE,CAAA;IACrE,gFAA2D,CAAA;IAE3D;;;;;;;;;;;;OAYG;IACH,wFAAmE,CAAA;AACvE,CAAC,EArBW,iBAAiB,iCAAjB,iBAAiB,QAqB5B"}
|
|
@@ -10,6 +10,20 @@ export declare enum RealtimeEventType {
|
|
|
10
10
|
DELIVERY_JOB_UPDATED = "delivery.job.updated",
|
|
11
11
|
MOBILITY_WORKER_UPDATED = "mobility.worker.updated",
|
|
12
12
|
MOBILITY_WORKER_LOCATION_UPDATED = "mobility.worker-location.updated",
|
|
13
|
-
MOBILITY_ASSIGNMENT_UPDATED = "mobility.assignment.updated"
|
|
13
|
+
MOBILITY_ASSIGNMENT_UPDATED = "mobility.assignment.updated",
|
|
14
|
+
/**
|
|
15
|
+
* An offer addressed to a worker changed, so their own offer list is stale.
|
|
16
|
+
*
|
|
17
|
+
* Carried on the **`mobility.worker` resource**, not an offer resource, and that is the whole
|
|
18
|
+
* point: a worker cannot subscribe to an offer that does not exist yet, and discovering new
|
|
19
|
+
* work is exactly the case realtime has to serve. They subscribe to themselves — the one
|
|
20
|
+
* identifier they hold before any offer is made — and refetch their self-scoped offer list.
|
|
21
|
+
*
|
|
22
|
+
* The event therefore names one resource while describing another aggregate, so its version
|
|
23
|
+
* must be the **offer's**, never the worker's. Publishing the worker's version here would
|
|
24
|
+
* repeat a value the profile events already used and be silently discarded by the outbox's
|
|
25
|
+
* uniqueness constraint. `mobility_worker_outbox_event.aggregate_type` exists for this.
|
|
26
|
+
*/
|
|
27
|
+
MOBILITY_DISPATCH_OFFER_UPDATED = "mobility.dispatch-offer.updated"
|
|
14
28
|
}
|
|
15
29
|
//# sourceMappingURL=realtime-event-type.enum.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"realtime-event-type.enum.d.ts","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,oBAAY,iBAAiB;IACzB,iBAAiB,sBAAsB;IACvC,oBAAoB,yBAAyB;IAC7C,uBAAuB,4BAA4B;IACnD,gCAAgC,qCAAqC;IACrE,2BAA2B,gCAAgC;
|
|
1
|
+
{"version":3,"file":"realtime-event-type.enum.d.ts","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,oBAAY,iBAAiB;IACzB,iBAAiB,sBAAsB;IACvC,oBAAoB,yBAAyB;IAC7C,uBAAuB,4BAA4B;IACnD,gCAAgC,qCAAqC;IACrE,2BAA2B,gCAAgC;IAE3D;;;;;;;;;;;;OAYG;IACH,+BAA+B,oCAAoC;CACtE"}
|
|
@@ -12,5 +12,19 @@ export var RealtimeEventType;
|
|
|
12
12
|
RealtimeEventType["MOBILITY_WORKER_UPDATED"] = "mobility.worker.updated";
|
|
13
13
|
RealtimeEventType["MOBILITY_WORKER_LOCATION_UPDATED"] = "mobility.worker-location.updated";
|
|
14
14
|
RealtimeEventType["MOBILITY_ASSIGNMENT_UPDATED"] = "mobility.assignment.updated";
|
|
15
|
+
/**
|
|
16
|
+
* An offer addressed to a worker changed, so their own offer list is stale.
|
|
17
|
+
*
|
|
18
|
+
* Carried on the **`mobility.worker` resource**, not an offer resource, and that is the whole
|
|
19
|
+
* point: a worker cannot subscribe to an offer that does not exist yet, and discovering new
|
|
20
|
+
* work is exactly the case realtime has to serve. They subscribe to themselves — the one
|
|
21
|
+
* identifier they hold before any offer is made — and refetch their self-scoped offer list.
|
|
22
|
+
*
|
|
23
|
+
* The event therefore names one resource while describing another aggregate, so its version
|
|
24
|
+
* must be the **offer's**, never the worker's. Publishing the worker's version here would
|
|
25
|
+
* repeat a value the profile events already used and be silently discarded by the outbox's
|
|
26
|
+
* uniqueness constraint. `mobility_worker_outbox_event.aggregate_type` exists for this.
|
|
27
|
+
*/
|
|
28
|
+
RealtimeEventType["MOBILITY_DISPATCH_OFFER_UPDATED"] = "mobility.dispatch-offer.updated";
|
|
15
29
|
})(RealtimeEventType || (RealtimeEventType = {}));
|
|
16
30
|
//# sourceMappingURL=realtime-event-type.enum.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"realtime-event-type.enum.js","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAN,IAAY,
|
|
1
|
+
{"version":3,"file":"realtime-event-type.enum.js","sourceRoot":"","sources":["../../../../src/api/realtime/realtime-event-type.enum.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAN,IAAY,iBAqBX;AArBD,WAAY,iBAAiB;IACzB,4DAAuC,CAAA;IACvC,kEAA6C,CAAA;IAC7C,wEAAmD,CAAA;IACnD,0FAAqE,CAAA;IACrE,gFAA2D,CAAA;IAE3D;;;;;;;;;;;;OAYG;IACH,wFAAmE,CAAA;AACvE,CAAC,EArBW,iBAAiB,KAAjB,iBAAiB,QAqB5B"}
|