chore: initial TransferGo CaseStudy

[Ferror]

Initial step for TransferGo case-study. Looking forward for suggestions and possible next steps 😄

Summary by CodeRabbit

• New Features

  • Added a TransferGo case study with a public AsyncAPI remittance event-bus spec, AWS SNS/SQS channels, and a sample remittance message (RemittanceTransactionRequested).
  • Introduces a comprehensive event catalog and published workflow for consuming and publishing remittance events.

• Documentation

  • Adds challenge/solution narratives, technical posture (architecture, CI/CD, contract testing, tooling), detailed remittance contract (sender/receiver, amount, currency, paymentMethod) and example payload.

[coderabbitai]

Walkthrough

Adds two new TransferGo case study artifacts: a YAML case study config at config/casestudies/transfergo.yml and an AsyncAPI spec at public/resources/casestudies/transfergo/asyncapi.yaml describing a remittance event bus, its schemas, channels (~300), and publishing/contract-testing workflows.

Changes

Cohort / File(s)	Summary
Case study config (new) config/casestudies/transfergo.yml	Adds TransferGo case study YAML with public metadata (id, company, website, logo, contact), challenges and solution narratives, detailed technical posture (languages, frameworks, brokers, SNS/SQS, Kafka, workers), schema management (storage, registry, versioning, validation), AsyncAPI ecosystem and publishing workflow (CI/CD, S3, Port.io), contract testing references (Microcks, LocalStack), tooling/extensions, and pointer to full AsyncAPI example.
AsyncAPI spec (new) public/resources/casestudies/transfergo/asyncapi.yaml	Adds AsyncAPI 3.0.0 spec for a Remittance Service Event Bus using AWS SNS/SQS. Defines AWS server variables (service enum: sns,sqs; region default us-east-1), two channels (remittance-transactions-topic, remittance-transactions-queue), publish/consume operations, RemittanceTransactionRequested message schema (required fields: transactionId (uuid), transactionType, createdAt (date-time), sender/receiver objects with name/email/country, amount (number), currency, paymentMethod enum), and an example payload.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant Repo as Git Repo
  participant CI as Jenkins CI
  participant Validator as AsyncAPI Validator
  participant S3 as S3 (artifact store)
  participant Portal as Port.io (Developer Portal)
  participant Catalog as Event Catalog
  participant CT as Contract Testing (Microcks/LocalStack)

  rect rgb(245,250,245)
    Note over Dev,Repo: Author and push case study + AsyncAPI spec
  end

  Dev->>Repo: push PR with `config/casestudies/transfergo.yml` and AsyncAPI
  Repo->>CI: trigger pipeline
  CI->>Validator: validate AsyncAPI + schemas
  Validator-->>CI: validation result

  alt validation success
    CI->>S3: upload AsyncAPI artifacts
    CI->>Portal: publish to Port.io
    Portal->>Catalog: register channels (~300)
    Catalog->>CT: invoke contract tests
    CT-->>CI: test/report results
  else validation failure
    CI->>Dev: report errors / fail job
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I twitch my whiskers, nose on the stream,
A YAML hop toward an async dream.
Topics bloom, queues hum in rows,
Pipelines fetch where the event wind blows.
I nudge a schema — the catalog grows. 🐰

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly indicates the primary change by adding the initial TransferGo case study, which matches the new configuration and AsyncAPI resources introduced in this pull request. It is concise, specific, and provides a clear summary of the main intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	785c2db
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68d4ef4ebdf6160008bac5b8
😎 Deploy Preview	https://deploy-preview-4409--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (78769a8) to head (785c2db).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4409   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (3)

config/casestudies/transfergo.yml (3)

22-23: Brand/style nits: “Port” and “EventCatalog”

Use “Port Developer Portal” (brand: Port) and “EventCatalog”. Minor, but improves consistency.

-  Schemas are stored in S3 and surfaced through Port.io Developer Portal
+  Schemas are stored in S3 and surfaced through Port Developer Portal
@@
-    Schemas are stored in GitHub repositories and automatically published to an S3 bucket. Port.io Developer Portal ingests these schemas
+    Schemas are stored in GitHub repositories and automatically published to an S3 bucket. Port Developer Portal ingests these schemas
@@
-    * [Port.io Developer Portal](https://port.io)
-    * [Event Catalog](https://www.eventcatalog.dev/)
+    * Port Developer Portal
+    * EventCatalog

Also applies to: 68-71, 85-86

---

20-25: CI tool references look mixed (Jenkins vs GH Actions)

You mention Jenkins (validation/testing) and GitHub Actions (publishing/validation). If both are true, clarify scope to avoid reader confusion; if not, pick the accurate one.

Also applies to: 68-71

---

27-33: Normalize language slugs across all case studies
Entries vary between “.NET” vs “.net”, “C#” vs no other C# usage, “node.js” vs potential “nodejs”, and inconsistent casing (“Java” vs “java”, “javascript” vs “JavaScript”). Align on a single taxonomy (e.g. dotnet, csharp, nodejs, javascript) to ensure validator compatibility.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7f53694 and ba23d1f.

⛔ Files ignored due to path filters (1)

• public/img/casestudies/transfergo/logo.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• config/casestudies/transfergo.yml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Validate case studies structures

config/casestudies/transfergo.yml

[error] 1-1: Step: actions/github-script@v6 - config/casestudies/transfergo.yml is invalid.

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Lighthouse CI
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Test NodeJS PR - macos-13

🔇 Additional comments (3)

config/casestudies/transfergo.yml (3)

9-9: Logo asset exists and path is correct

Verified that public/img/casestudies/transfergo/logo.svg is present and the configured path /img/casestudies/transfergo/logo.svg will render without errors.

---

6-8: Standardize customers and industry fields

• customers values vary (e.g. "5000", 500M, "over 8 million"); align with schema (likely a numeric string)
• industry should match the defined enum (e.g. Insurance, Retail, Fintech) without free-text or slashes

Confirm the case-studies schema/types and update config/casestudies/transfergo.yml accordingly.

---

1-1: All case study IDs match their filenames and are unique—no changes required.

[derberg]

@Ferror thanks a lot for the PR

you need to followup and provide full example as a file under resources/casestudies/transfergo/asyncapi.yaml

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	39
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-4409--asyncapi-website.netlify.app/

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

public/resources/casestudies/transfergo/asyncapi.yaml (1)

1-140: Validate AsyncAPI spec and fix config path linkage.

• config/casestudies/transfergo.yml (line 78) references resources/casestudies/transfergo/asyncapi.yaml but the actual file is at public/resources/casestudies/transfergo/asyncapi.yaml — update the config to the public/... path or move/symlink the file so the referenced path exists.
• AsyncAPI validation did not run: asyncapi CLI not found. Ensure asyncapi is installed in dev/CI and run asyncapi validate public/resources/casestudies/transfergo/asyncapi.yaml and fix any schema errors before merging.

🧹 Nitpick comments (5)

public/resources/casestudies/transfergo/asyncapi.yaml (5)

26-46: Add AWS bindings for SNS topic and SQS queue.

Bindings make this portable and actionable in tooling.

   sns/remittance-transactions-topic:
     description: SNS topic for remittance transaction events.
+    bindings:
+      sns:
+        topicName: remittance-transactions-topic
+        fifo: false
+        rawMessageDelivery: true
     publish:
       operationId: publishRemittanceTransactionToSNS
       summary: Publish RemittanceTransactionRequested event to SNS topic
       message:
         $ref: '#/components/messages/RemittanceTransactionRequested'

   sqs/remittance-transactions-queue:
     description: SQS queue that receives messages forwarded from SNS topic via subscription.
+    bindings:
+      sqs:
+        queueName: remittance-transactions-queue
+        fifo: false
+        visibilityTimeout: 30
+        deadLetter:
+          enabled: false
     subscribe:
       operationId: consumeRemittanceTransactionFromSQS
       summary: Consumer service polls SQS to consume RemittanceTransactionRequested events.
+      bindings:
+        sqs:
+          batch:
+            maxMessages: 10
       message:
         $ref: '#/components/messages/RemittanceTransactionRequested'

---

11-24: Add AWS SigV4 security (and consider explicit SNS/SQS servers).

If you keep protocol=https, declare SigV4 so docs are accurate. Optionally split servers for SNS and SQS.

 servers:
   aws:
     url: 'https://{service}.{region}.amazonaws.com'
     protocol: https
     description: AWS endpoints for SNS and SQS.
     variables:
       service:
         enum:
           - sns
           - sqs
         default: sns
       region:
         default: us-east-1
         description: AWS region used for the SNS/SQS resources.
+    security:
+      - awsSigV4: []
+
+components:
+  securitySchemes:
+    awsSigV4:
+      type: apiKey
+      in: header
+      name: Authorization
+      description: AWS Signature Version 4 Authorization header (also requires x-amz-date).

---

48-122: Tighten the message contract: correlationId, headers, and schema constraints.

Strengthens observability and reduces invalid payloads.

   messages:
     RemittanceTransactionRequested:
       name: RemittanceTransactionRequested
       title: Remittance Transaction Requested
       summary: Event emitted when a user requests to send money cross-border.
       contentType: application/json
+      headers:
+        type: object
+        properties:
+          x-trace-id:
+            type: string
+            description: End-to-end trace identifier.
+      correlationId:
+        description: Correlates all events for a given transaction.
+        location: "$message.payload#/transactionId"
       payload:
         type: object
         required:
           - transactionId
           - transactionType
           - createdAt
           - sender
           - receiver
           - amount
           - currency
           - paymentMethod
         properties:
           transactionId:
             type: string
             format: uuid
             description: Unique transaction identifier.
           transactionType:
-            type: string
-            description: Type of transaction.
+            type: string
+            description: Type of transaction.
+            enum: ["remittance.requested"]
           createdAt:
             type: string
             format: date-time
             description: ISO8601 timestamp for when the request was made.
           sender:
             type: object
             required:
               - name
               - email
               - country
             properties:
               name:
                 type: string
               email:
                 type: string
                 format: email
               country:
                 type: string
                 description: ISO 3166-1 alpha-2 country code
+                pattern: '^[A-Z]{2}$'
           receiver:
             type: object
             required:
               - name
               - email
               - country
             properties:
               name:
                 type: string
               email:
                 type: string
                 format: email
               country:
                 type: string
                 description: ISO 3166-1 alpha-2 country code
+                pattern: '^[A-Z]{2}$'
           amount:
             type: number
             format: double
             description: Amount requested to transfer.
+            exclusiveMinimum: 0
           currency:
             type: string
             description: ISO 4217 currency code.
+            pattern: '^[A-Z]{3}$'
           paymentMethod:
             type: string
             description: Payment method used to fund the transaction.
             enum:
               - card
               - wire_transfer
               - bank_account

---

79-107: DRY sender/receiver with reusable schemas.

Define Party once and $ref it to avoid drift.

 components:
+  schemas:
+    Party:
+      type: object
+      required: [name, email, country]
+      properties:
+        name: { type: string }
+        email: { type: string, format: email }
+        country: { type: string, pattern: '^[A-Z]{2}$', description: ISO 3166-1 alpha-2 country code }
   messages:
     RemittanceTransactionRequested:
       ...
       payload:
         type: object
         properties:
           sender:
-            type: object
-            required: [name, email, country]
-            properties: { ... }
+            $ref: '#/components/schemas/Party'
           receiver:
-            type: object
-            required: [name, email, country]
-            properties: { ... }
+            $ref: '#/components/schemas/Party'

Also applies to: 100-107

---

1-4: Upgrade AsyncAPI to v3.0.1 and use v3-compatible tooling

v3.0.1 (released 2023-12-13) is the latest stable spec and is supported by official AsyncAPI tooling — update public/resources/casestudies/transfergo/asyncapi.yaml (asyncapi: '3.0.1') and ensure the site uses v3-capable packages (e.g. @asyncapi/parser 3.x, generator/react component updates); if your site cannot use v3 tooling yet, keep 2.6.0.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0eb3ac0 and 2ff6525.

📒 Files selected for processing (1)

• public/resources/casestudies/transfergo/asyncapi.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (6)

public/resources/casestudies/transfergo/asyncapi.yaml (6)

11-24: Consider separate servers for SNS and SQS for clarity.

Splitting the single templated server into two named servers improves readability and tool UX (explicit target per channel).

Apply:

-servers:
-  aws:
-    url: 'https://{service}.{region}.amazonaws.com'
-    protocol: https
-    description: AWS endpoints for SNS and SQS.
-    variables:
-      service:
-        enum:
-          - sns
-          - sqs
-        default: sns
-      region:
-        default: us-east-1
-        description: AWS region used for the SNS/SQS resources.
+servers:
+  sns:
+    url: 'https://sns.{region}.amazonaws.com'
+    protocol: https
+    description: AWS SNS endpoint.
+    variables:
+      region:
+        default: us-east-1
+        description: AWS region used for the SNS topic.
+  sqs:
+    url: 'https://sqs.{region}.amazonaws.com'
+    protocol: https
+    description: AWS SQS endpoint.
+    variables:
+      region:
+        default: us-east-1
+        description: AWS region used for the SQS queue.

---

104-106: Drop non‑portable number format.

format: double isn’t defined in JSON Schema and can trigger tooling warnings. Use plain number (optional constraints if needed).

           amount:
             type: number
-            format: double
             description: Amount requested to transfer.

---

86-88: Add basic format validation for country and currency codes.

Enforce ISO shapes to catch typos early.

               country:
                 type: string
-                description: ISO 3166-1 alpha-2 country code
+                description: ISO 3166-1 alpha-2 country code
+                pattern: '^[A-Z]{2}$'
...
               country:
                 type: string
-                description: ISO 3166-1 alpha-2 country code
+                description: ISO 3166-1 alpha-2 country code
+                pattern: '^[A-Z]{2}$'
...
           currency:
             type: string
             description: ISO 4217 currency code.
+            pattern: '^[A-Z]{3}$'

Also applies to: 100-103, 108-109

---

61-116: Tighten schema: amount lower bound and optional enums.

• Add a minimum for positive transfers.
• Consider constraining transactionType if it follows a known taxonomy.

           transactionType:
             type: string
             description: Type of transaction.
+            # enum: [remittance.requested]  # uncomment if taxonomy is fixed
...
           amount:
             type: number
             description: Amount requested to transfer.
+            minimum: 0.01
+            exclusiveMinimum: true

---

45-49: Consider message headers and correlation ID for tracing/idempotency.

Model a correlation ID (and optional traceparent) in headers to support SQS redeliveries and cross‑service tracing.

     RemittanceTransactionRequested:
       name: RemittanceTransactionRequested
       title: Remittance Transaction Requested
       summary: Event emitted when a user requests to send money cross-border.
       contentType: application/json
+      headers:
+        type: object
+        properties:
+          x-correlation-id:
+            type: string
+            description: Correlates related events/requests.
+          traceparent:
+            type: string
+            description: W3C Trace Context header.
+      correlationId:
+        description: Correlates messages for a single transaction/request.
+        location: "$message.headers#/x-correlation-id"

Please validate the JSON Pointer for correlationId with your AsyncAPI tooling (Studio/CLI) to ensure compatibility.

---

35-41: Document at‑least‑once and idempotency at the consumer.

SQS delivers at‑least‑once and may redeliver; suggest noting idempotent consumption keyed by transactionId.

You can append a short note to the subscribe operation summary/description about deduplication/idempotency expectations.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2ff6525 and d684d57.

📒 Files selected for processing (1)

• public/resources/casestudies/transfergo/asyncapi.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Test NodeJS PR - macos-13

🔇 Additional comments (2)

public/resources/casestudies/transfergo/asyncapi.yaml (2)

26-41: Correct SNS publish and SQS subscribe semantics.

Good fix: the producer publishes to SNS and the consumer subscribes to SQS; broker fan‑out isn’t modeled as an app publish.

---

117-135: Good, realistic example payload.

Covers all required fields and matches schema; helpful for docs and tests.

[derberg]

looking great https://deploy-preview-4409--asyncapi-website.netlify.app/casestudies/transfergo ❤️

I left you some feedback in DM. One more thing, can you please add links to tools, especially open source, that you mention in the PR? when published on the website, especially so popular like ours, it is good for the open source projects to get better SEO results. You know, links to their websites, if they exists of course, like the one for Microcks and Event Catalog, and if it doesn't, then GH link

[derberg]

well done, can't wait to see the blog post

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (5)

config/casestudies/transfergo.yml (5)

22-22: Brand/style consistency and linking: “Port Developer Portal”

Use official naming and add a link on first mention.

-  For accessibility, TransferGo automated publishing of AsyncAPI definitions using GitHub Actions. Schemas are stored in S3 and surfaced through Port.io Developer Portal, providing a single interface for developers to browse, search, and visualize service contracts.
+  For accessibility, TransferGo automated publishing of AsyncAPI definitions using GitHub Actions. Schemas are stored in S3 and surfaced through the [Port Developer Portal](https://www.port.io/), providing a single interface for developers to browse, search, and visualize service contracts.

---

61-62: Reference “Port Developer Portal” consistently

Align naming and link.

-    Schemas are stored in GitHub repositories and automatically published to an S3 bucket. Port.io Developer Portal ingests these schemas to make them accessible to developers.
+    Schemas are stored in GitHub repositories and automatically published to an S3 bucket. The [Port Developer Portal](https://www.port.io/) ingests these schemas to make them accessible to developers.

---

73-73: Reference “Port Developer Portal” consistently

Align naming and link.

-    AsyncAPI React component was initially used for rendering. Today, Port.io Developer Portal serves as the central platform, presenting all AsyncAPI schemas in a unified, visual interface.
+    AsyncAPI React component was initially used for rendering. Today, the [Port Developer Portal](https://www.port.io/) serves as the central platform, presenting all AsyncAPI schemas in a unified, visual interface.

---

41-42: Add links for tools mentioned in narrative (SEO + clarity)

Link Microcks and LocalStack here too.

-  testing: |
-    Contract testing with Microcks and LocalStack integrated into Jenkins CI, validating message-driven services without requiring cloud infrastructure.
+  testing: |
+    Contract testing with [Microcks](https://microcks.io/) and [LocalStack](https://www.localstack.cloud/) integrated into Jenkins CI, validating message-driven services without requiring cloud infrastructure.

---

27-33: Normalize casing for languages/runtimes

Improves consistency.

   languages:
-    - php
-    - .NET
-    - C#
-    - javascript
-    - node.js
+    - PHP
+    - C#
+    - .NET
+    - JavaScript
+    - Node.js

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 865b336 and 785c2db.

📒 Files selected for processing (1)

• config/casestudies/transfergo.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Redirect rules - asyncapi-website

🔇 Additional comments (5)

config/casestudies/transfergo.yml (5)

40-40: brokers should be a YAML list (not a comma-separated string)

Prevents schema/type validation failures.

-  brokers: AWS SNS/SQS, Kafka
+  brokers:
+    - AWS SNS
+    - AWS SQS
+    - Kafka

---

51-51: registry should be null (avoid prose in scalar field)

Keep distribution details in storage/documentation.

-  registry: None, schemas are distributed via S3 and Port.io Developer Portal.
+  registry: null

---

55-58: asyncapi.usecase must be a list, not a block string

YAML block string won’t pass list validation.

-  usecase: |
-    TransferGo uses AsyncAPI to unify async API documentation across services, generate schemas from code via internal libraries, validate and optimize schemas in CI pipelines, publish schemas to Port.io Developer Portal for centralized access, build an [Event Catalog](https://www.eventcatalog.dev/) for visibility into 300+ channels, and support contract testing with [Microcks](https://microcks.io/).
+  usecase:
+    - Unify async API documentation across services.
+    - Generate schemas from code via internal libraries.
+    - Validate and optimize schemas in CI pipelines.
+    - Publish schemas to the Port Developer Portal for centralized access.
+    - Build an Event Catalog for visibility into 300+ channels.
+    - Support contract testing with Microcks.

---

70-75: Replace “None” block scalars with empty lists for extensions/bindings

Avoids type mismatches.

-  extensions: |
-    None
+  extensions: []
   documentation: |
     AsyncAPI React component was initially used for rendering. Today, Port.io Developer Portal serves as the central platform, presenting all AsyncAPI schemas in a unified, visual interface.
-  bindings: |
-    None
+  bindings: []

---

76-77: tools should be an array, not a markdown block

Keep it as a list of names; links are already present in narrative text for SEO.

-  tools: |
-    TransferGo relies on [AsyncAPI CLI](https://github.com/asyncapi/cli), [AsyncAPI React](https://github.com/asyncapi/asyncapi-react), [AsyncAPI Modelina](https://github.com/asyncapi/modelina), [Port.io Developer Portal](https://www.port.io/), [Event Catalog](https://www.eventcatalog.dev/), [Microcks](https://microcks.io/), [LocalStack](https://github.com/localstack/localstack), and API Guardian (internal CLI).
+  tools:
+    - AsyncAPI CLI
+    - AsyncAPI React
+    - Modelina
+    - Port Developer Portal
+    - Event Catalog
+    - Microcks
+    - LocalStack
+    - API Guardian

[coderabbitai]

🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

Verify fullExample path resolves (likely needs leading slash)

The AsyncAPI file appears at public/resources/casestudies/transfergo/asyncapi.yaml. Config usually references it as “/resources/...”.

If needed:

-  fullExample: resources/casestudies/transfergo/asyncapi.yaml
+  fullExample: /resources/casestudies/transfergo/asyncapi.yaml

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Configured path in YAML:"
rg -nC0 -N '^  fullExample:' config/casestudies/transfergo.yml

echo
echo "Check if file exists at repo path:"
fd -a 'asyncapi.yaml' public | sed 's#^# - #'

echo
echo "Recommend updating to a leading-slash web path if the site expects public-rooted URLs."

Length of output: 425

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Listing fullExample in other case study configs:"
rg -n "fullExample:" config/casestudies/*.yml

Length of output: 321

---

Prefix fullExample paths with a leading slash in all case study configs

Each AsyncAPI file lives under public/resources/…, so fullExample must start with “/resources/…”.

• config/casestudies/transfergo.yml (line 78)

  - fullExample: resources/casestudies/transfergo/asyncapi.yaml
  + fullExample: /resources/casestudies/transfergo/asyncapi.yaml

• config/casestudies/hdi.yml (line 232)

  - fullExample: resources/casestudies/hdi/asyncapi.yaml
  + fullExample: /resources/casestudies/hdi/asyncapi.yaml

• config/casestudies/adeo.yml (line 278)

  - fullExample: resources/casestudies/adeo/asyncapi.yaml
  + fullExample: /resources/casestudies/adeo/asyncapi.yaml

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	fullExample: resources/casestudies/transfergo/asyncapi.yaml
	fullExample: /resources/casestudies/transfergo/asyncapi.yaml

🤖 Prompt for AI Agents

In config/casestudies/transfergo.yml around line 78, the fullExample path is
missing a leading slash; update the value from
"resources/casestudies/transfergo/asyncapi.yaml" to start with
"/resources/casestudies/transfergo/asyncapi.yaml" so the path points to
public/resources/...; apply the same leading-slash convention to other case
study config files noted in the review.

[derberg]

/rtm