@eventcatalog/create-eventcatalog 0.1.0 → 0.1.4

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.
@@ -4,6 +4,7 @@ module.exports = {
4
4
  organizationName: 'Your Company',
5
5
  projectName: 'Event Catalog',
6
6
  editUrl: 'https://github.com/boyney123/eventcatalog-demo/edit/master',
7
+ trailingSlash: true,
7
8
  logo: {
8
9
  alt: 'EventCatalog Logo',
9
10
  // found in the public dir
@@ -12,6 +13,7 @@ module.exports = {
12
13
  footerLinks: [
13
14
  { label: 'Events', href: '/events' },
14
15
  { label: 'Services', href: '/services' },
16
+ { label: 'Visualiser', href: '/visualiser' },
15
17
  { label: '3D Node Graph', href: '/overview' },
16
18
  { label: 'GitHub', href: 'https://github.com/boyney123/eventcatalog-demo/edit/master' }
17
19
  ],
@@ -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 the final event of the ordering process. It gets raised when the shipment has been delivered.
20
20
 
21
- ### Consumer / Producer Diagram
22
-
23
- <Mermaid />
21
+ <NodeGraph title="Consumer / Producer Diagram" />
24
22
 
25
23
  <Schema />
@@ -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
- ### Consumer / Producer Diagram
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
- ### Consumer / Producer Diagram
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
- ### Consumer / Producer Diagram
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
- ### Consumer / Producer Diagram
27
-
28
- <Mermaid />
26
+ <NodeGraph title="Consumer / Producer Diagram" />
29
27
 
30
28
  <Schema />
@@ -19,8 +19,6 @@ owners:
19
19
 
20
20
  This event is triggered when a shipment has been delievered to it's destination.
21
21
 
22
- ### Consumer / Producer Diagram
23
-
24
- <Mermaid />
22
+ <NodeGraph title="Consumer / Producer Diagram" />
25
23
 
26
24
  <Schema />
@@ -18,8 +18,6 @@ owners:
18
18
 
19
19
  This event is triggered when a shipment has been dispatched from the warehouse.
20
20
 
21
- ### Consumer / Producer Diagram
22
-
23
- <Mermaid />
21
+ <NodeGraph title="Consumer / Producer Diagram" />
24
22
 
25
23
  <Schema />
@@ -18,8 +18,6 @@ owners:
18
18
 
19
19
  This event is triggered when a shipment has finished being prepared.
20
20
 
21
- ### Consumer / Producer Diagram
22
-
23
- <Mermaid />
21
+ <NodeGraph title="Consumer / Producer Diagram" />
24
22
 
25
23
  <Schema />
@@ -7,6 +7,7 @@
7
7
 
8
8
  # Generated files
9
9
  .next
10
+ out
10
11
 
11
12
 
12
13
  # Misc
@@ -13,4 +13,4 @@ Simple API that handles interactions between users and their baskets. Use this s
13
13
 
14
14
  This service will also generate Async events for downstream services.
15
15
 
16
- <Mermaid />
16
+ <NodeGraph />
@@ -8,4 +8,4 @@ owners:
8
8
 
9
9
  Our internal Data Lake platform used by the data team to consume events of our Architecture and provide valuable insights and analytics.
10
10
 
11
- <Mermaid />
11
+ <NodeGraph />
@@ -10,4 +10,4 @@ The payment service is our own internal payment service that listens to events f
10
10
 
11
11
  We use Stripe to handle services and use this Payment service to enrich events for internal use.
12
12
 
13
- <Mermaid />
13
+ <NodeGraph />
@@ -13,4 +13,4 @@ Event based service that allows you to create shipments, prepare them and dispat
13
13
 
14
14
  This service will also generate Async events for downstream services.
15
15
 
16
- <Mermaid />
16
+ <NodeGraph />
package/dist/gitignore CHANGED
@@ -7,6 +7,7 @@
7
7
 
8
8
  # Generated files
9
9
  .next
10
+ out
10
11
 
11
12
 
12
13
  # Misc