@eventcatalog/create-eventcatalog 3.0.13 → 3.1.3

package/templates/default/domains/Payment/services/PaymentService/events/PaymentProcessed/index.mdx

@@ -4,11 +4,7 @@ name: Payment Processed
 version: 1.0.0
 summary: Event is triggered after the payment has been successfully processed
 owners:
-    - dboyne
-channels:
-  - id: payments.{env}.events
-    parameters:
-      env: staging
+  - dboyne
 ---
 
 import Footer from '@catalog/components/footer.astro';
@@ -43,4 +39,4 @@ The PaymentProcessed event is triggered after the payment has been successfully
 - **Sensitive Data Handling**: Avoid including sensitive information (e.g., full credit card numbers) in the event payload. Use secure channels and encryption for such data.
 - **Authentication and Authorization**: Ensure that only authorized services can publish or consume PaymentProcessed events.
 
-<Footer />
+<Footer />

package/templates/default/domains/Payment/services/PaymentService/index.mdx

@@ -5,18 +5,25 @@ version: 0.0.1
 summary: |
   Service that handles payments
 owners:
-    - dboyne
+  - dboyne
 receives:
   - id: PaymentInitiated
     version: 0.0.1
+    from:
+      - id: 'payments.{env}.events'
+        parameters:
+          env: staging
   - id: GetPaymentStatus
 sends:
   - id: PaymentProcessed
     version: 0.0.1
-  - id: GetOrder
+    to:
+      - id: 'payments.{env}.events'
+        parameters:
+          env: staging
 repository:
   language: JavaScript
-  url: https://github.com/event-catalog/pretend-shipping-service
+  url: 'https://github.com/event-catalog/pretend-shipping-service'
 ---
 
 The Payment Service is a crucial component of our system that handles all payment-related operations. It processes payments, manages transactions, and communicates with other services through events. Using an event-driven architecture, it ensures that all actions are asynchronous, decoupled, and scalable.
@@ -30,4 +37,4 @@ The Payment Service is a crucial component of our system that handles all paymen
 - Payment Gateway: Interfaces with external payment providers.
 - Transaction Service: Manages transaction records and states.
 - Notification Service: Sends notifications related to payment status changes.
-- Database: Stores transaction data and payment status.
+- Database: Stores transaction data and payment status.

package/templates/default/domains/Subscriptions/services/BillingService/index.mdx

@@ -2,22 +2,22 @@
 id: BillingService
 version: 0.0.1
 name: Billing Service
-summary: Manages billing cycles, invoice generation, and payment scheduling for subscriptions
+summary: >-
+  Manages billing cycles, invoice generation, and payment scheduling for
+  subscriptions
 tags:
   - billing
   - subscriptions
   - invoicing
 repository:
-  url: https://github.com/eventcatalog/billing-service
+  url: 'https://github.com/eventcatalog/billing-service'
 receives:
-  - id: SubscriptionCreated
-    version: 0.0.1
-  - id: SubscriptionUpdated
-    version: 0.0.1
   - id: PaymentProcessed
     version: 0.0.1
-  - id: PaymentFailed
-    version: 0.0.1
+    from:
+      - id: 'payments.{env}.events'
+        parameters:
+          env: staging
 sends:
   - id: InvoiceGenerated
     version: 0.0.1
@@ -83,4 +83,4 @@ billing_service:
   invoice_generation_lead_days: 7
 ```
 
-<Footer />
+<Footer />

package/templates/index.ts

@@ -139,7 +139,6 @@ export const installTemplate = async ({
       switch (name) {
         case "env":
         case "gitignore":
-        case "env":
         case "npmrc":
         case "dockerignore":
         case "eslintrc.json": {