Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Jun 2, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Bug Fixes
    • Corrected repository URLs for Specmatic to ensure accurate linking.
  • Documentation
    • Enhanced descriptions for Mokapi to highlight customizable test data generation features.
    • Improved and clarified metadata, descriptions, and categorization for various AsyncAPI tools to ensure accuracy and consistency.
  • Chores
    • Reordered and updated tool listings for better organization and relevance.

@netlify
Copy link

netlify bot commented Jun 2, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit f1981ab
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/683cf30be50bf40009604125
😎 Deploy Preview https://deploy-preview-4142--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 2, 2025

Walkthrough

This update modifies several JSON configuration files to swap, correct, and update metadata for various tools and technology tags. Changes include swapping names in technology tags, reorganizing tool entries, updating descriptions, repository URLs, and adjusting categorization and metadata for AsyncAPI-related tools.

Changes

File(s) Summary of Changes
config/all-tags.json Swapped "name" values of "SmartPaste" and "JetBrains" entries in the "technologies" array.
config/tools-automated.json Reorganized, swapped, and corrected metadata for multiple AsyncAPI tools: titles, descriptions, URLs, tags, categories, and flags.
config/tools.json Updated Mokapi's description to include test data generator info; fixed Specmatic's repository URL.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant JSON Config
    participant Website

    User->>JSON Config: Request technology/tool metadata
    JSON Config-->>Website: Provide updated tool and technology data
    Website-->>User: Display updated names, descriptions, and URLs
Loading

Possibly related PRs

  • chore: update tools.json #4048: Modifies the same JSON configuration files by swapping and updating tool metadata, directly related to changes in tool entries and tags.
  • chore: update tools.json #4108: Involves swapping and updating entries in the same JSON configuration files with nearly identical changes to names, URLs, and descriptions.
  • chore: update tools.json #4117: Swaps the "name" values of "SmartPaste" and "JetBrains" in config/all-tags.json, overlapping directly with this change.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • akshatnema
  • anshgoyalevil
  • sambhavgupta0705
  • Mayaleeeee
  • devilkiller-ag
  • vishvamsinh28
  • asyncapi-bot-eve

Poem

A rabbit hopped through JSON fields,
Swapping names with careful yields.
URLs aligned, descriptions bright,
Tools now listed just right.
With every hop, the data grew neat—
AsyncAPI’s garden, tidy and sweet!
🐇✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link

codecov bot commented Jun 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (9c52752) to head (f1981ab).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4142   +/-   ##
=========================================
  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.

@asyncapi-bot asyncapi-bot merged commit 8913133 into master Jun 2, 2025
32 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-tools/regenerateTools branch June 2, 2025 00:44
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🔭 Outside diff range comments (1)
config/all-tags.json (1)

285-289: ⚠️ Potential issue

Remove redundant duplicate "SmartPaste" tag
The SmartPaste entry appears twice in succession, leading to duplicate tags. Please remove the redundant block to maintain a unique list of technologies.

Apply this diff:

-    {
-      "name": "SmartPaste",
-      "color": "bg-[#61d0f2]",
-      "borderColor": "border-[#40ccf7]"
-    },
🧹 Nitpick comments (10)
config/tools-automated.json (10)

94-98: Nitpick: Normalize "AsyncApi" to "AsyncAPI" in description
The description uses "AsyncApi" instead of the standard "AsyncAPI" acronym. For consistency, update the casing.

Apply:

- "description": "The officially maintained fork of the AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common (de)serializers to extract raw AsyncApi JSON and YAML documents from the model.",
+ "description": "The officially maintained fork of the AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common (de)serializers to extract raw AsyncAPI JSON and YAML documents from the model.",

165-174: Optional: Use consistent language tag ("Go" vs "golang")
The language field is set to "golang", whereas other Go entries use "Go". Consider normalizing to "Go" for consistency.

Apply:

- "language": "golang",
+ "language": "Go",

180-190: Optional: Normalize casing and URL consistency

  • Change "language": "python" to "Python".
  • Change "amqp" to "AMQP".
  • (Optional) Remove trailing slash from repoUrl for consistency.

Apply:

- "language": "python",
+ "language": "Python",

- "amqp"
+ "AMQP"

- "repoUrl": "https://github.com/G-USI/asyncapi-python/",
+ "repoUrl": "https://github.com/G-USI/asyncapi-python"

220-239: Optional: Deduplicate repeated "ZenWave SDK" entries
The "ZenWave SDK" tool appears in multiple categories (Code Generators, Mocking and Testing, CLI). Consider maintaining a single definition and filtering by categories rather than duplicating the entire object.


531-547: Optional: Normalize language tag to "Go"
The language field is listed as "Go/Golang". For consistency, consider using "Go" only.

Apply:

- "language": "Go/Golang",
+ "language": "Go",

554-574: Optional: Deduplicate repeated "ZenWave SDK" entries
This tool is listed here and in other categories. Consolidate definitions to a single entry with a multi-valued categories filter.


607-611: Nitpick: Normalize "AsyncApi" to "AsyncAPI" in description
Mirrors the change in Code-first: correct casing of the AsyncAPI acronym.

Apply:

- "description": "The officially maintained fork of the AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common (de)serializers to extract raw AsyncApi JSON and YAML documents from the model.",
+ "description": "The officially maintained fork of the AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common (de)serializers to extract raw AsyncAPI JSON and YAML documents from the model.",

713-717: Optional: Consolidate "Mokapi" descriptions across categories
The description field here duplicates the entry under Mocking and Testing. Consider referencing a single source or pulling common metadata to avoid drift.


754-779: Optional: Deduplicate repeated "ZenWave SDK" entries
As with Code Generators and Mocking and Testing, this CLI entry duplicates the same tool. Use a single definition filtered by categories.


810-821: Nitpick: Capitalize "IDEA" and standardize naming

  • Change "description": "Idea plugin..." to "description": "IDEA plugin...".
  • Consider aligning the title to "jAsyncAPI IDEA Plugin" for consistency.

Apply:

- "description": "Idea plugin for the java-asyncapi - Helps to edit and validate AsyncAPI schemas.",
+ "description": "IDEA plugin for the java-asyncapi – helps edit and validate AsyncAPI schemas.",
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c52752 and f1981ab.

📒 Files selected for processing (3)
  • config/all-tags.json (1 hunks)
  • config/tools-automated.json (21 hunks)
  • config/tools.json (3 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (3)
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Lighthouse CI
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (4)
config/all-tags.json (1)

276-284: Swap "JetBrains" and "SmartPaste" entries
The metadata for the two adjacent technology tags has been correctly swapped.

config/tools.json (2)

1771-1778: Enhance Mokapi description with test data generator details
The updated description now highlights Mokapi’s powerful, fully customizable JavaScript-based test data generator—this aligns with the tool’s capabilities.


1841-1844: Correct Specmatic repository URL
The repoUrl has been updated to point at the official specmatic/specmatic repository.

config/tools-automated.json (1)

514-517:

Details

✅ Verification successful

Verify: Corrected Specmatic repoUrl
The repoUrl was updated; ensure the new URL resolves correctly and that the docsUrl and websiteUrl are still valid.

Run:


🏁 Script executed:

#!/bin/bash
set -e
# Verify Specmatic repo URL returns HTTP 200
curl -I https://github.com/specmatic/specmatic | head -n 1

Length of output: 508


Let's also verify the websiteUrl and docsUrl:


🏁 Script executed:

#!/bin/bash
set -e
# Verify Specmatic website URL returns HTTP 200
curl -I https://specmatic.io | head -n 1
# Verify Specmatic docs URL returns HTTP 200
curl -I https://specmatic.io/documentation/ | head -n 1

Length of output: 768


Specmatic URLs are valid and reachable
All three links—repoUrl, websiteUrl, and docsUrl—respond with HTTP 200 as expected. No further action required.

• config/tools-automated.json (lines 514–517)

Comment on lines +72 to 77
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET/",
"repoUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET"
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Critical: Description references OpenAPI instead of AsyncAPI
The description for this LEGO fork of the SDK incorrectly mentions "OpenAPI JSON and YAML". It should reference "AsyncAPI JSON and YAML" to accurately describe the SDK.

Apply:

- "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
+ "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw AsyncAPI JSON and YAML documents from the model.",
📝 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
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET/",
"repoUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET"
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
},
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw AsyncAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
},
🤖 Prompt for AI Agents
In config/tools-automated.json around lines 72 to 77, the description
incorrectly mentions "OpenAPI JSON and YAML" instead of "AsyncAPI JSON and
YAML". Update the description text to replace "OpenAPI" with "AsyncAPI" to
accurately reflect the SDK's purpose.

Comment on lines +585 to +589
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET/",
"repoUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET"
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Critical: Description references OpenAPI instead of AsyncAPI
Same issue as in the Code-first category: the description mentions "OpenAPI". Update it to "AsyncAPI".

Apply:

- "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
+ "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw AsyncAPI JSON and YAML documents from the model.",
📝 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
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET/",
"repoUrl": "https://github.com/ByteBardOrg/AsyncAPI.NET"
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
"title": "AsyncAPI.Net",
- "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
+ "description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw AsyncAPI JSON and YAML documents from the model.",
"links": {
"websiteUrl": "https://github.com/LEGO/AsyncAPI.NET/",
"repoUrl": "https://github.com/LEGO/AsyncAPI.NET"
🤖 Prompt for AI Agents
In config/tools-automated.json around lines 585 to 589, the description
incorrectly references "OpenAPI" instead of "AsyncAPI". Update the description
text to replace "OpenAPI" with "AsyncAPI" to accurately reflect the AsyncAPI.NET
SDK's purpose.

Comment on lines +831 to +839
"title": "asyncapi-preview",
"description": "VSCode extension that enables you to:\n - Preview documentation generated using you AsyncAPI document. It uses AsyncAPI React component under the hood,\n - Create AsyncAPI documents faster using SmartPaste functionality\n",
"links": {
"websiteUrl": "https://plugins.jetbrains.com/plugin/15673-asyncapi",
"docsUrl": "https://github.com/asyncapi/jasyncapi-idea-plugin#usage",
"repoUrl": "https://github.com/asyncapi/jasyncapi-idea-plugin"
"repoUrl": "https://github.com/asyncapi/vs-asyncapi-preview"
},
"filters": {
"language": "Kotlin",
"technology": [
"JetBrains",
"IntelliJ IDEA"
"VSCode",
"SmartPaste"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Critical: Fix grammar and title casing

  • Title asyncapi-preview should be "AsyncAPI Preview" in Title Case.
  • In the description, change "using you AsyncAPI document" to "using your AsyncAPI document".

Apply:

- "title": "asyncapi-preview",
+ "title": "AsyncAPI Preview",

- "description": "VSCode extension that enables you to:\n  - Preview documentation generated using you AsyncAPI document. It uses AsyncAPI React component under the hood,\n  - Create AsyncAPI documents faster using SmartPaste functionality\n",
+ "description": "VSCode extension that enables you to:\n  - Preview documentation generated using your AsyncAPI document (uses AsyncAPI React under the hood)\n  - Create AsyncAPI documents faster using SmartPaste functionality\n",
📝 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
"title": "asyncapi-preview",
"description": "VSCode extension that enables you to:\n - Preview documentation generated using you AsyncAPI document. It uses AsyncAPI React component under the hood,\n - Create AsyncAPI documents faster using SmartPaste functionality\n",
"links": {
"websiteUrl": "https://plugins.jetbrains.com/plugin/15673-asyncapi",
"docsUrl": "https://github.com/asyncapi/jasyncapi-idea-plugin#usage",
"repoUrl": "https://github.com/asyncapi/jasyncapi-idea-plugin"
"repoUrl": "https://github.com/asyncapi/vs-asyncapi-preview"
},
"filters": {
"language": "Kotlin",
"technology": [
"JetBrains",
"IntelliJ IDEA"
"VSCode",
"SmartPaste"
"title": "AsyncAPI Preview",
"description": "VSCode extension that enables you to:\n - Preview documentation generated using your AsyncAPI document (uses AsyncAPI React under the hood)\n - Create AsyncAPI documents faster using SmartPaste functionality\n",
"links": {
"repoUrl": "https://github.com/asyncapi/vs-asyncapi-preview"
},
"filters": {
"technology": [
"VSCode",
"SmartPaste"
🤖 Prompt for AI Agents
In config/tools-automated.json around lines 831 to 839, update the title from
"asyncapi-preview" to "AsyncAPI Preview" using proper title casing. Also, in the
description, correct the phrase "using you AsyncAPI document" to "using your
AsyncAPI document" to fix the grammar.

aminoxix pushed a commit to aminoxix/asyncapi-website that referenced this pull request Jun 4, 2025
This was referenced Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants