@eventcatalog/create-eventcatalog 0.2.1 → 0.2.4

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

@@ -1,6 +1,5 @@
 ---
 name: Shopping
-version: 0.0.1
 summary: |
   Domain for everything shopping
 owners:
@@ -8,12 +7,10 @@ owners:
     - 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>
+<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 event can be triggered multiple times per customer. Everytime the customer adds an item to their shopping cart this event will be triggered.
+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.
 
-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" />
+<NodeGraph title="Domain Graph" />

package/dist/default/eventcatalog.config.js

@@ -5,6 +5,14 @@ module.exports = {
   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

package/dist/default/services/Payment Service/index.md

@@ -10,4 +10,6 @@ The payment service is our own internal payment service that listens to events f
 
 We use Stripe to handle services and use this Payment service to enrich events for internal use.
 
-<NodeGraph />
+<OpenAPI />
+
+<NodeGraph />

package/dist/default/services/Payment Service/openapi.yaml

@@ -0,0 +1,94 @@
+openapi: 3.0.0
+info:
+  description: A Payment Service API
+  version: 0.0.1
+  title: Payment service API
+servers:
+  - url: http://payment.example.com/v1
+    description: Optional server description, e.g. Main (production) server
+  - url: http://payment.example.com
+    description: Optional server description, e.g. Internal staging server for testing
+paths:
+  /getSinglePaymentURL:
+    get:
+      tags:
+        - PaymentServices
+      summary: Generate a Payment endpoint URL
+      operationId: singlepaymenturlUsingGET
+      consumes:
+        - application/json
+      produces:
+        - application/xml
+      parameters:
+        - name: transType
+          in: query
+          description: transType
+          required: true
+          type: string
+        - name: invoiceNumber
+          in: query
+          description: invoiceNumber
+          required: true
+          type: string
+        - name: approvedPage
+          in: query
+          description: approvedPage
+          required: true
+          type: string
+        - name: declinedPage
+          in: query
+          description: declinedPage
+          required: true
+          type: string
+        - in: query
+          name: errorPage
+          description: errorPage
+          required: true
+          type: string
+        - in: query
+          name: totalItemsAmount
+          description: totalItemsAmount
+          required: true
+          type: string
+        - name: ref1
+          in: query
+          description: ref1
+          required: false
+          type: string
+        - name: ref2
+          in: query
+          description: ref2
+          required: false
+          type: string
+        - name: ref3
+          in: query
+          description: ref3
+          required: false
+          type: string
+        - name: minutesToExpire
+          in: query
+          description: minutesToExpire
+          required: true
+          type: string
+      responses:
+        '200':
+          description: Successful operation
+          schema:
+            $ref: '#/definitions/SinglePaymentResponse'
+        '401':
+          description: Unauthorized
+        '403':
+          description: Forbidden
+        '404':
+          description: Not Found
+definitions:
+  SinglePaymentResponse:
+    type: object
+    properties:
+      respCode:
+        type: integer
+        format: int32
+      respMsg:
+        type: string
+      respValue:
+        type: string