@reventlessdev/online-shop-dcb-ordering 1.0.0-alpha.103 → 1.0.0-alpha.104

package/CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# 1.0.0-alpha.104 (2026-06-29)
+
+### Features
+
+* external-system boxes for translation slices (Event Graph data) ([3f8ad39](https://github.com/ReventlessDev/reventless-core/commit/3f8ad39b78a3cb1182d59a0e1fb203b7dcb7379b))
+
+
 # 1.0.0-alpha.103 (2026-06-27)
 
 **Note:** Version bump only for package @reventlessdev/online-shop-dcb-ordering

package/lib/bs/.compiler.log

@@ -1,2 +1,2 @@
-#Start(1782549921109)
-#Done(1782549923116)
+#Start(1782764560099)
+#Done(1782764562048)

package/lib/bs/compiler-info.json

@@ -4,5 +4,5 @@
   "bsc_hash": "75e3a59c95cc953608fd3dd6ea6ed68141bba4414a20a52f114261b8a48385fa",
   "rescript_config_hash": "2b45634c4ef9d26c69e2cd8282eb5d077ce9cf087ded0065001d0f0d889e241c",
   "runtime_path": "/home/runner/work/reventless-core/reventless-core/node_modules/@rescript/runtime",
-  "generated_at": "1782549923133"
+  "generated_at": "1782764562064"
 }

package/lib/bs/src/Order/AutomationSlice/AutoShipOrder_Automation.res

@@ -1,8 +1,6 @@
 @@reventless.automation
 
 // Single DCB source — events from the ordering plugin's own event log.
-// `module Id = Reventless.Id.String` and dcbTags on `*Id` fields are
-// auto-injected by `@@reventless.automation` (Source-module scan).
 module OrderingDcbSource = {
   let name = "OrderingDcbEventLog"
   @schema

package/lib/bs/src/Order/OutboundTranslationSlice/SendOrderConfirmation.res

@@ -17,3 +17,6 @@ type inboundCommand = unit
 let maxRetries = 3
 let heartbeatInterval = 60
 let targetName = None
+// Foreign system this anti-corruption slice publishes confirmations to — drawn as an
+// external box outside the Ordering plugin in the Event Graph.
+let externalSystem = Some("EmailService")

package/lib/bs/src/Order/OutboundTranslationSlice/SendOrderConfirmation.res.mjs

@@ -26,6 +26,8 @@ let heartbeatInterval = 60;
 
 let targetName;
 
+let externalSystem = "EmailService";
+
 let moduleUrl = "@reventlessdev/online-shop-dcb-ordering/src/Order/OutboundTranslationSlice/SendOrderConfirmation.res.mjs";
 
 export {
@@ -37,6 +39,7 @@ export {
   maxRetries,
   heartbeatInterval,
   targetName,
+  externalSystem,
   moduleUrl,
 }
 /* consumedEventSchema Not a pure module */

package/lib/bs/src/Order/StateChangeSlice/CancelOrder.res

@@ -19,6 +19,7 @@ type error =
 
 @schema
 type event = OrderCancelled({
+  // orderId and productIds both tag — @partitionTag picks the storage partition.
   @partitionTag orderId: string,
   productIds: array<string>,
 })

package/lib/bs/src/Order/StateChangeSlice/PlaceOrder.res

@@ -1,19 +1,9 @@
 // PlaceOrder StateChangeSlice.
 // Handles the PlaceOrder command; rejects duplicate placement and validates
 // that all referenced products have been synced to the ordering event log.
-//
-// The tagged array `productIds: array<string>` triggers automatic multi-clause
-// query construction: one OR clause per orderId and per productId element —
-// fetching both Order and CatalogProduct events. The plural field name is
-// auto-singularised by the PPX so each element is stored under tag key
-// `productId`, sharing the key with single-value `productId: string` producers.
 
 @@reventless.spec
 
-// `OrderPlaced` carries `orderId` (not partial) so the decision model can
-// discriminate placements across the multi-clause query. Without it,
-// OrderPlaced events from sibling orders that share a `productId` tag would
-// leak in and falsely set "this order exists".
 @schema
 type consumedEvent =
   | OrderPlaced({orderId: string})
@@ -21,6 +11,7 @@ type consumedEvent =
 
 @schema
 type command =
+  // Multiple tagged fields — @partitionTag picks orderId as the storage partition.
   PlaceOrder({@partitionTag orderId: string, customerId: string, @ref("AvailableProducts") productIds: array<string>})
 
 @schema

package/lib/bs/src/Order/StateChangeSlice/PlaceOrder.res.mjs

@@ -19,7 +19,7 @@ let commandSchema = S.schema(s => ({
   TAG: "PlaceOrder",
   orderId: s.m(DcbTag$Reventless.partition),
   customerId: s.m(DcbTag$Reventless.string),
-  productIds: s.m(S.array(Reference$Reventless.to_(undefined, "productId", "AvailableProducts")))
+  productIds: s.m(S.array(Reference$Reventless.to_(undefined, undefined, "AvailableProducts")))
 }));
 
 let errorSchema = S.union([

package/lib/bs/src/Order/StateChangeSlice/PlaceOrder_Behavior.res

@@ -1,13 +1,8 @@
 @@reventless.behavior
 
-// `placedOrderIds` tracks every OrderPlaced the query returned (regardless of
-// orderId — the multi-clause query also fetches by productId tags), so the
-// `decide` step can ask "is THIS particular orderId already placed?" without
-// being confused by OrderPlaced events from sibling orders sharing a product.
-//
-// Stored as immutable arrays (rather than `Set.t`) so each fold yields a
-// fresh state — `evolve` returns a new record instead of mutating a shared
-// one. This keeps successive `decide` calls (and unit tests) hermetic.
+// Stored as immutable arrays (rather than `Set.t`) so each fold yields a fresh
+// state — `evolve` returns a new record instead of mutating a shared one. This
+// keeps successive `decide` calls (and unit tests) hermetic.
 type state = {placedOrderIds: array<string>, availableProductIds: array<string>}
 
 let initialState = {placedOrderIds: [], availableProductIds: []}

package/lib/bs/src/Plugin.res.mjs

@@ -222,7 +222,8 @@ function Make(Platform) {
     inboundCommandSchema: SendOrderConfirmation$OrderingPlugin.inboundCommandSchema,
     maxRetries: SendOrderConfirmation$OrderingPlugin.maxRetries,
     heartbeatInterval: SendOrderConfirmation$OrderingPlugin.heartbeatInterval,
-    targetName: undefined
+    targetName: undefined,
+    externalSystem: SendOrderConfirmation$OrderingPlugin.externalSystem
   })({
     collect: SendOrderConfirmation_Translation$OrderingPlugin.collect,
     translate: SendOrderConfirmation_Translation$OrderingPlugin.translate,

package/lib/bs/tests/Order/OutboundTranslationSlice/SendOrderConfirmation_GWT.res.mjs

@@ -13,6 +13,7 @@ let SendOrderConfirmationSlice = {
   maxRetries: SendOrderConfirmation$OrderingPlugin.maxRetries,
   heartbeatInterval: SendOrderConfirmation$OrderingPlugin.heartbeatInterval,
   targetName: undefined,
+  externalSystem: SendOrderConfirmation$OrderingPlugin.externalSystem,
   moduleUrl: SendOrderConfirmation$OrderingPlugin.moduleUrl,
   collect: SendOrderConfirmation_Translation$OrderingPlugin.collect
 };

package/lib/ocaml/.compiler.log

@@ -1,2 +1,2 @@
-#Start(1782549921109)
-#Done(1782549923116)
+#Start(1782764560099)
+#Done(1782764562048)

package/lib/ocaml/AutoShipOrder_Automation.res

@@ -1,8 +1,6 @@
 @@reventless.automation
 
 // Single DCB source — events from the ordering plugin's own event log.
-// `module Id = Reventless.Id.String` and dcbTags on `*Id` fields are
-// auto-injected by `@@reventless.automation` (Source-module scan).
 module OrderingDcbSource = {
   let name = "OrderingDcbEventLog"
   @schema

package/lib/ocaml/CancelOrder.res

@@ -19,6 +19,7 @@ type error =
 
 @schema
 type event = OrderCancelled({
+  // orderId and productIds both tag — @partitionTag picks the storage partition.
   @partitionTag orderId: string,
   productIds: array<string>,
 })

package/lib/ocaml/PlaceOrder.res

@@ -1,19 +1,9 @@
 // PlaceOrder StateChangeSlice.
 // Handles the PlaceOrder command; rejects duplicate placement and validates
 // that all referenced products have been synced to the ordering event log.
-//
-// The tagged array `productIds: array<string>` triggers automatic multi-clause
-// query construction: one OR clause per orderId and per productId element —
-// fetching both Order and CatalogProduct events. The plural field name is
-// auto-singularised by the PPX so each element is stored under tag key
-// `productId`, sharing the key with single-value `productId: string` producers.
 
 @@reventless.spec
 
-// `OrderPlaced` carries `orderId` (not partial) so the decision model can
-// discriminate placements across the multi-clause query. Without it,
-// OrderPlaced events from sibling orders that share a `productId` tag would
-// leak in and falsely set "this order exists".
 @schema
 type consumedEvent =
   | OrderPlaced({orderId: string})
@@ -21,6 +11,7 @@ type consumedEvent =
 
 @schema
 type command =
+  // Multiple tagged fields — @partitionTag picks orderId as the storage partition.
   PlaceOrder({@partitionTag orderId: string, customerId: string, @ref("AvailableProducts") productIds: array<string>})
 
 @schema

package/lib/ocaml/PlaceOrder_Behavior.res

@@ -1,13 +1,8 @@
 @@reventless.behavior
 
-// `placedOrderIds` tracks every OrderPlaced the query returned (regardless of
-// orderId — the multi-clause query also fetches by productId tags), so the
-// `decide` step can ask "is THIS particular orderId already placed?" without
-// being confused by OrderPlaced events from sibling orders sharing a product.
-//
-// Stored as immutable arrays (rather than `Set.t`) so each fold yields a
-// fresh state — `evolve` returns a new record instead of mutating a shared
-// one. This keeps successive `decide` calls (and unit tests) hermetic.
+// Stored as immutable arrays (rather than `Set.t`) so each fold yields a fresh
+// state — `evolve` returns a new record instead of mutating a shared one. This
+// keeps successive `decide` calls (and unit tests) hermetic.
 type state = {placedOrderIds: array<string>, availableProductIds: array<string>}
 
 let initialState = {placedOrderIds: [], availableProductIds: []}

package/lib/ocaml/SendOrderConfirmation.res

@@ -17,3 +17,6 @@ type inboundCommand = unit
 let maxRetries = 3
 let heartbeatInterval = 60
 let targetName = None
+// Foreign system this anti-corruption slice publishes confirmations to — drawn as an
+// external box outside the Ordering plugin in the Event Graph.
+let externalSystem = Some("EmailService")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/online-shop-dcb-ordering",
-  "version": "1.0.0-alpha.103",
+  "version": "1.0.0-alpha.104",
   "description": "Online Shop example — Ordering bounded context (Customer & Order) using the DCB pattern",
   "license": "Apache-2.0",
   "jest": {
@@ -21,18 +21,18 @@
   },
   "dependencies": {
     "sury": "^11.0.0-alpha.4",
-    "@reventlessdev/online-shop-dcb-ordering-spec": "1.0.0-alpha.58",
-    "@reventlessdev/online-shop-dcb-catalog-spec": "1.0.0-alpha.58",
+    "@reventlessdev/online-shop-dcb-catalog-spec": "1.0.0-alpha.59",
+    "@reventlessdev/online-shop-dcb-ordering-spec": "1.0.0-alpha.59",
     "@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.14",
-    "@reventlessdev/reventless-gwt": "1.0.0-alpha.74",
-    "@reventlessdev/reventless-infra": "3.0.0-alpha.81",
-    "@reventlessdev/reventless-local": "3.0.0-alpha.113",
-    "@reventlessdev/reventless-spec": "3.0.0-alpha.61"
+    "@reventlessdev/reventless-infra": "3.0.0-alpha.82",
+    "@reventlessdev/reventless-gwt": "1.0.0-alpha.75",
+    "@reventlessdev/reventless-local": "3.0.0-alpha.114",
+    "@reventlessdev/reventless-spec": "3.0.0-alpha.62"
   },
   "devDependencies": {
     "rescript": "^12.3.0",
     "sury-ppx": "11.0.0-alpha.2",
-    "@reventlessdev/reventless-ppx": "1.0.0-alpha.47"
+    "@reventlessdev/reventless-ppx": "1.0.0-alpha.48"
   },
   "peerDependencies": {
     "rescript": "^12.3.0"

package/src/Order/AutomationSlice/AutoShipOrder_Automation.res

@@ -1,8 +1,6 @@
 @@reventless.automation
 
 // Single DCB source — events from the ordering plugin's own event log.
-// `module Id = Reventless.Id.String` and dcbTags on `*Id` fields are
-// auto-injected by `@@reventless.automation` (Source-module scan).
 module OrderingDcbSource = {
   let name = "OrderingDcbEventLog"
   @schema

package/src/Order/OutboundTranslationSlice/SendOrderConfirmation.res

@@ -17,3 +17,6 @@ type inboundCommand = unit
 let maxRetries = 3
 let heartbeatInterval = 60
 let targetName = None
+// Foreign system this anti-corruption slice publishes confirmations to — drawn as an
+// external box outside the Ordering plugin in the Event Graph.
+let externalSystem = Some("EmailService")

package/src/Order/StateChangeSlice/CancelOrder.res

@@ -19,6 +19,7 @@ type error =
 
 @schema
 type event = OrderCancelled({
+  // orderId and productIds both tag — @partitionTag picks the storage partition.
   @partitionTag orderId: string,
   productIds: array<string>,
 })

package/src/Order/StateChangeSlice/PlaceOrder.res

@@ -1,19 +1,9 @@
 // PlaceOrder StateChangeSlice.
 // Handles the PlaceOrder command; rejects duplicate placement and validates
 // that all referenced products have been synced to the ordering event log.
-//
-// The tagged array `productIds: array<string>` triggers automatic multi-clause
-// query construction: one OR clause per orderId and per productId element —
-// fetching both Order and CatalogProduct events. The plural field name is
-// auto-singularised by the PPX so each element is stored under tag key
-// `productId`, sharing the key with single-value `productId: string` producers.
 
 @@reventless.spec
 
-// `OrderPlaced` carries `orderId` (not partial) so the decision model can
-// discriminate placements across the multi-clause query. Without it,
-// OrderPlaced events from sibling orders that share a `productId` tag would
-// leak in and falsely set "this order exists".
 @schema
 type consumedEvent =
   | OrderPlaced({orderId: string})
@@ -21,6 +11,7 @@ type consumedEvent =
 
 @schema
 type command =
+  // Multiple tagged fields — @partitionTag picks orderId as the storage partition.
   PlaceOrder({@partitionTag orderId: string, customerId: string, @ref("AvailableProducts") productIds: array<string>})
 
 @schema

package/src/Order/StateChangeSlice/PlaceOrder_Behavior.res

@@ -1,13 +1,8 @@
 @@reventless.behavior
 
-// `placedOrderIds` tracks every OrderPlaced the query returned (regardless of
-// orderId — the multi-clause query also fetches by productId tags), so the
-// `decide` step can ask "is THIS particular orderId already placed?" without
-// being confused by OrderPlaced events from sibling orders sharing a product.
-//
-// Stored as immutable arrays (rather than `Set.t`) so each fold yields a
-// fresh state — `evolve` returns a new record instead of mutating a shared
-// one. This keeps successive `decide` calls (and unit tests) hermetic.
+// Stored as immutable arrays (rather than `Set.t`) so each fold yields a fresh
+// state — `evolve` returns a new record instead of mutating a shared one. This
+// keeps successive `decide` calls (and unit tests) hermetic.
 type state = {placedOrderIds: array<string>, availableProductIds: array<string>}
 
 let initialState = {placedOrderIds: [], availableProductIds: []}