@eventcatalog/create-eventcatalog 0.0.5 → 0.1.3
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/default/eventcatalog.config.js +1 -0
- package/dist/default/events/AddedItemToCart/index.md +4 -5
- package/dist/default/events/OrderComplete/index.md +1 -3
- package/dist/default/events/OrderConfirmed/index.md +1 -3
- package/dist/default/events/OrderRequested/index.md +1 -3
- package/dist/default/events/PaymentProcessed/index.md +1 -3
- package/dist/default/events/RemovedItemFromCart/index.md +1 -3
- package/dist/default/events/ShipmentDelivered/index.md +1 -3
- package/dist/default/events/ShipmentDispatched/index.md +1 -3
- package/dist/default/events/ShipmentPrepared/index.md +1 -3
- package/dist/default/gitignore +3 -0
- package/dist/default/services/Basket Service/index.md +1 -1
- package/dist/default/services/Data Lake/index.md +1 -1
- package/dist/default/services/Payment Service/index.md +1 -1
- package/dist/default/services/Shipping Service/index.md +1 -1
- package/dist/gitignore +3 -0
- package/dist/index.js +1 -1
- package/package.json +1 -1
|
@@ -22,11 +22,10 @@ This event can be triggered multiple times per customer. Everytime the customer
|
|
|
22
22
|
|
|
23
23
|
We have a frontend application that allows users to buy things from our store. This front end interacts directly with the `Basket Service` to add items to the cart. The `Basket Service` will raise the events.
|
|
24
24
|
|
|
25
|
-
|
|
26
|
-
### Consumer / Producer Diagram
|
|
27
|
-
|
|
28
|
-
<Mermaid />
|
|
25
|
+
<NodeGraph title="Consumer / Producer Diagram" />
|
|
29
26
|
|
|
30
27
|
<EventExamples title="How to trigger event" />
|
|
31
28
|
|
|
32
|
-
<Schema />
|
|
29
|
+
<Schema />
|
|
30
|
+
|
|
31
|
+
<SchemaViewer renderRootTreeLines defaultExpandedDepth='0' maxHeight="500" />
|
|
@@ -18,8 +18,6 @@ owners:
|
|
|
18
18
|
|
|
19
19
|
This event is triggered when the customers order has been verified and the stock has been checked. Once this event is triggered we are safe to say it is ready for shipment.
|
|
20
20
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
<Mermaid />
|
|
21
|
+
<NodeGraph title="Consumer / Producer Diagram" />
|
|
24
22
|
|
|
25
23
|
<Schema />
|
|
@@ -20,8 +20,6 @@ This event is triggered when the user confirms their order and wants to process
|
|
|
20
20
|
|
|
21
21
|
We have a frontend application that allows users to buy things from our store. The frontend application interacts with the Backet Service to trigger the `OrderRequested` event.
|
|
22
22
|
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
<Mermaid />
|
|
23
|
+
<NodeGraph title="Consumer / Producer Diagram" />
|
|
26
24
|
|
|
27
25
|
<Schema />
|
|
@@ -20,8 +20,6 @@ This event is triggered when the payment has succesfully been processed for a cu
|
|
|
20
20
|
|
|
21
21
|
We use Stripe to handle customer payments. The Payment Service listens for Stripe webhooks and raises the PaymentProcessed event.
|
|
22
22
|
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
<Mermaid />
|
|
23
|
+
<NodeGraph title="Consumer / Producer Diagram" />
|
|
26
24
|
|
|
27
25
|
<Schema />
|
|
@@ -23,8 +23,6 @@ This event can be triggered multiple times per customer. Everytime the customer
|
|
|
23
23
|
We have a frontend application that allows users to buy things from our store. This front end interacts directly with the `Basket Service` to add items to the cart. The `Basket Service` will raise the events.
|
|
24
24
|
|
|
25
25
|
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
<Mermaid />
|
|
26
|
+
<NodeGraph title="Consumer / Producer Diagram" />
|
|
29
27
|
|
|
30
28
|
<Schema />
|
package/dist/default/gitignore
CHANGED