@eventcatalog/create-eventcatalog 1.2.1 → 2.0.0

package/dist/default/domains/Shopping/events/AddedItemToCart/versioned/0.0.1/index.md

@@ -1,28 +0,0 @@
----
-name: AddedItemToCart
-version: 0.0.1
-summary: |
-  Holds information about what the user added to their shopping cart.
-producers:
-    - Basket Service
-consumers:
-    - Data Lake
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event can be triggered multiple times per customer. Everytime the customer adds an item to their shopping cart this event will be triggered.
-
-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.
-
-
-### Consumer / Producer Diagram
-
-<Mermaid />
-
-<Schema />

package/dist/default/domains/Shopping/events/AddedItemToCart/versioned/0.0.1/schema.json

@@ -1,39 +0,0 @@
-{
-  "$id": "https://example.com/AddedItemToCart.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "AddedItemToCart",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "itemId": {
-          "type": "string",
-          "description": "The ID of the shopping item"
-        }
-      }
-    }
-  }
-}

package/dist/default/domains/Shopping/events/AddedItemToCart/versioned/0.0.2/index.md

@@ -1,28 +0,0 @@
----
-name: AddedItemToCart
-version: 0.0.1
-summary: |
-  Holds information about what the user added to their shopping cart.
-producers:
-    - Basket Service
-consumers:
-    - Data Lake
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event can be triggered multiple times per customer. Everytime the customer adds an item to their shopping cart this event will be triggered.
-
-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.
-
-
-### Consumer / Producer Diagram
-
-<Mermaid />
-
-<Schema />

package/dist/default/domains/Shopping/events/AddedItemToCart/versioned/0.0.2/schema.json

@@ -1,46 +0,0 @@
-{
-  "$id": "https://example.com/AddedItemToCart.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "AddedItemToCart",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "itemId": {
-          "type": "string",
-          "description": "The ID of the shopping item"
-        },
-        "quantity": {
-          "type": "number",
-          "description": "How many items the user wants to add to their shopping cart",
-          "minimum": 1,
-          "maximum": 100,
-          "default": 1
-        }
-      }
-    }
-  }
-}

package/dist/default/domains/Shopping/events/RemovedItemFromCart/index.md

@@ -1,26 +0,0 @@
----
-name: RemovedItemFromCart
-version: 0.0.1
-summary: |
-  Holds information about what the user removed from their cart.
-producers:
-    - Basket Service
-consumers:
-    - Data Lake
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event can be triggered multiple times per customer. Everytime the customer adds an item to their shopping cart this event will be triggered.
-
-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.
-
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/domains/Shopping/events/RemovedItemFromCart/schema.json

@@ -1,46 +0,0 @@
-{
-  "$id": "https://example.com/RemovedItemFromCart.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "RemovedItemFromCart",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "itemId": {
-          "type": "string",
-          "description": "The ID of the shopping item"
-        },
-        "quantity": {
-          "type": "number",
-          "description": "How many items the user wants to remove to their shopping cart",
-          "minimum": 1,
-          "maximum": 100,
-          "default": 1
-        }
-      }
-    }
-  }
-}

package/dist/default/domains/Shopping/index.md

@@ -1,16 +0,0 @@
----
-name: Shopping
-summary: |
-  Domain for everything shopping
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>Domain for everything to do with Shopping at our business. Before adding any events or services to this domain make sure you contact the domain owners and verify it's the correct place.</Admonition>
-
-### Details
-
-This domain encapsulates everything in our business that has to do with shopping and users. This might be new items added to our online shop or online cart management.
-
-<NodeGraph title="Domain Graph" />

package/dist/default/eventcatalog.config.js

@@ -1,50 +0,0 @@
-module.exports = {
-  title: 'EventCatalog',
-  tagline: 'Discover, Explore and Document your Event Driven Architectures',
-  organizationName: 'Your Company',
-  projectName: 'Event Catalog',
-  editUrl: 'https://github.com/boyney123/eventcatalog-demo/edit/master',
-  trailingSlash: true,
-  primaryCTA: {
-    label: 'Explore Events',
-    href: '/events'
-  },
-  secondaryCTA: {
-    label: 'Getting Started',
-    href:"https://www.eventcatalog.dev/"
-  },
-  logo: {
-    alt: 'EventCatalog Logo',
-    // found in the public dir
-    src: 'logo.svg',
-  },
-  headerLinks: [
-    { label: 'Events', href: '/events'},
-    { label: 'Services', href: '/services' },
-    { label: 'Domains', href: '/domains'},
-    { label: 'Users', href: '/users'},
-    { label: 'Visualiser', href: '/visualiser' },
-    { label: '3D Node Graph', href: '/overview' },
-  ],
-  footerLinks: [
-    { label: 'Events', href: '/events' },
-    { label: 'Services', href: '/services' },
-    { label: 'Visualiser', href: '/visualiser' },
-    { label: '3D Node Graph', href: '/overview' },
-    { label: 'GitHub', href: 'https://github.com/boyney123/eventcatalog-demo/edit/master' }
-  ],
-  users: [
-    {
-      id: 'dboyne',
-      name: 'David Boyne',
-      avatarUrl: 'https://pbs.twimg.com/profile_images/1262283153563140096/DYRDqKg6_400x400.png',
-      role: 'Developer',
-    },
-    {
-      id: 'mSmith',
-      name: 'Matthew Smith',
-      avatarUrl: 'https://randomuser.me/api/portraits/lego/3.jpg',
-      role: 'Developer',
-    },
-  ],
-}

package/dist/default/eventcatalog.styles.css

@@ -1,15 +0,0 @@
-
-/**
-
-Stylesheet overrides for EventCatalog. 
-There is currently a limit on what can be changed. 
-
-If you want to override some styles of particular elements, raise an issue for discussion. (https://github.com/boyney123/eventcatalog)
-
-Note: Override based on custom selectors / hacks at your own risk. EventCatalog selectors will change over time, which may break your styles.
-      use the styles marked with `ec-` for non breaking styling changes
-
-*/
-.ec-homepage{
-    background:black;
-}

package/dist/default/events/OrderComplete/index.md

@@ -1,23 +0,0 @@
----
-name: OrderComplete
-version: 0.0.1
-summary: |
-  Event represents when an order has been complete. (Delivered and finished)
-producers:
-    - Orders Service
-consumers:
-    - Data Lake
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event is the final event of the ordering process. It gets raised when the shipment has been delivered.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/events/OrderComplete/schema.json

@@ -1,39 +0,0 @@
-{
-  "$id": "https://example.com/OrderRequested.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "OrderRequested",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain", "service"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "orderId": {
-          "type": "string",
-          "description": "The ID the users order"
-        }
-      }
-    }
-  }
-}

package/dist/default/events/OrderConfirmed/index.md

@@ -1,23 +0,0 @@
----
-name: OrderConfirmed
-version: 0.0.1
-summary: |
-  Event represents when an order has been confirmed and ready to be processed (shipped for example)
-producers:
-    - Orders Service
-consumers:
-    - Shipping Service
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-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.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/events/OrderConfirmed/schema.json

@@ -1,39 +0,0 @@
-{
-  "$id": "https://example.com/OrderRequested.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "OrderRequested",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain", "service"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "orderId": {
-          "type": "string",
-          "description": "The ID the users order"
-        }
-      }
-    }
-  }
-}

package/dist/default/events/OrderRequested/index.md

@@ -1,25 +0,0 @@
----
-name: OrderRequested
-version: 0.0.1
-summary: |
-  Holds information about the customers order.
-producers:
-    - Basket Service
-consumers:
-    - Payment Service
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event is triggered when the user confirms their order and wants to process their payment.
-
-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.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/events/OrderRequested/schema.json

@@ -1,39 +0,0 @@
-{
-  "$id": "https://example.com/OrderRequested.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "OrderRequested",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain", "service"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "orderId": {
-          "type": "string",
-          "description": "The ID the users order"
-        }
-      }
-    }
-  }
-}

package/dist/default/events/PaymentProcessed/index.md

@@ -1,25 +0,0 @@
----
-name: PaymentProcessed
-version: 0.0.1
-summary: |
-  Holds information about the payment that has been processed.
-producers:
-    - Payment Service
-consumers:
-    - Orders Service
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event is triggered when the payment has succesfully been processed for a customers orders.
-
-We use Stripe to handle customer payments. The Payment Service listens for Stripe webhooks and raises the PaymentProcessed event.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/events/PaymentProcessed/schema.json

@@ -1,43 +0,0 @@
-{
-  "$id": "https://example.com/PaymentProcessed.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "PaymentProcessed",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain", "service"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "orderId": {
-          "type": "string",
-          "description": "The ID the users order"
-        },
-        "stripeId": {
-          "type": "string",
-          "description": "The ID the payment handled in stripe"
-        }
-      }
-    }
-  }
-}

package/dist/default/events/ShipmentDelivered/index.md

@@ -1,24 +0,0 @@
----
-name: ShipmentDelivered
-version: 0.0.1
-summary: |
-  Event represents when a shipment has been delievered and received.
-producers:
-    - Shipping Service
-consumers:
-    - Order Service
-    - Data Lake
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event is triggered when a shipment has been delievered to it's destination.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />

package/dist/default/events/ShipmentDelivered/schema.json

@@ -1,43 +0,0 @@
-{
-  "$id": "https://example.com/ShipmentDispatched.json",
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "title": "ShipmentDispatched",
-  "type": "object",
-  "properties": {
-    "metadata": {
-      "type": "object",
-      "properties": {
-        "correlationId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "domain": {
-          "type": "string",
-          "description": "The domain of the event"
-        },
-        "service": {
-          "type": "string",
-          "description": "The name of the service that triggered the event"
-        }
-      },
-      "required": ["correlationId", "domain", "service"]
-    },
-    "data": {
-      "type": "object",
-      "properties": {
-        "userId": {
-          "type": "string",
-          "description": "The ID of the user"
-        },
-        "shipmentId": {
-          "type": "string",
-          "description": "The ID of the shipment"
-        },
-        "orderId": {
-          "type": "string",
-          "description": "The order assigned to the shipment"
-        }
-      }
-    }
-  }
-}

package/dist/default/events/ShipmentDispatched/index.md

@@ -1,23 +0,0 @@
----
-name: ShipmentDispatched
-version: 0.0.1
-summary: |
-  Event represents when a shipment has been dispatched.
-producers:
-    - Shipping Service
-consumers:
-    - Shipping Service
-owners:
-    - dboyne
-    - mSmith
----
-
-<Admonition>When firing this event make sure you set the `correlation-id` in the headers. Our schemas have standard metadata make sure you read and follow it.</Admonition>
-
-### Details
-
-This event is triggered when a shipment has been dispatched from the warehouse.
-
-<NodeGraph title="Consumer / Producer Diagram" />
-
-<Schema />