Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

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

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Updated and reordered AsyncAPI tool listings for improved accuracy and consistency in categories, technologies, and metadata.
    • Corrected repository URLs and ownership information for several tools and extensions.
    • Removed duplicate entries and adjusted tool positions within categories.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 14, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The changes update and reorder entries in three JSON configuration files for AsyncAPI tools and technologies. Adjustments include correcting tool metadata, categories, languages, technologies, ownership flags, and repository URLs, removing duplicates, and swapping entries for consistency. No code logic is altered, as the modifications are limited to configuration data for tool listings and references.

Changes

Files Change Summary
config/tools-automated.json Reordered and updated tool entries; corrected metadata (categories, languages, technologies); fixed ownership flags; removed duplicates; swapped entries within sections; updated repository URLs; ensured consistency across all tool categories.
config/tools.json Swapped and corrected repository URLs and descriptions for AsyncAPI CLI, GitHub Action for Generator, and asyncapi-preview VSCode extension entries; toggled category tags; no other metadata changed.
config/all-tags.json Swapped the order and names of two technology entries: "Socket.IO" and "TypeScript," preserving color and borderColor values.

Sequence Diagram(s)

No sequence diagram generated, as changes are limited to static configuration data.

Possibly related PRs

Suggested reviewers

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

Poem

🐇
Hopping through configs, neat and spry,
Swapping URLs as I pass by.
Tools reordered, tags in line,
Ownership flags now all align.
In JSON fields I leap and play—
AsyncAPI shines today!


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6fe75e6 and ab41668.

📒 Files selected for processing (3)
  • config/all-tags.json (1 hunks)
  • config/tools-automated.json (24 hunks)
  • config/tools.json (9 hunks)

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.

@netlify
Copy link

netlify bot commented Jun 14, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit ab41668
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/684db315f8a94e00082f3833
😎 Deploy Preview https://deploy-preview-4181--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.

@codecov
Copy link

codecov bot commented Jun 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (1f17528) to head (ab41668).

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

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: 1

🧹 Nitpick comments (4)
config/tools.json (2)

2354-2354: Clarify community fork entry
The secondary AsyncAPI CLI entry now points to the community fork at https://github.com/hkirat/asyncapi-fork. Consider distinguishing this in the title or description (e.g., "AsyncAPI CLI (community fork)") to avoid confusion.


3035-3035: Differentiate community fork in "Others"
The community fork entry under Others points to https://github.com/hkirat/asyncapi-fork. As above, consider clarifying in the title or description that this is a community-maintained fork.

config/tools-automated.json (2)

1016-1028: Suggest differentiating duplicate AsyncAPI CLI title
Two entries under Others share the exact title "AsyncAPI CLI". Consider appending a qualifier (e.g., "(fork)") to one to avoid user confusion.


1034-1047: Suggest appending qualifier to CLI fork title
The forked CLI entry should be distinguishable from the official one—e.g., "AsyncAPI CLI (fork)".

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1f17528 and 6fe75e6.

📒 Files selected for processing (2)
  • config/tools-automated.json (18 hunks)
  • config/tools.json (6 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (5)
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Lighthouse CI
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Test NodeJS PR - ubuntu-latest
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (23)
config/tools.json (4)

2331-2331: Confirm official CLI repo link
The primary AsyncAPI CLI entry’s repoUrl has been updated to https://github.com/asyncapi/cli. This aligns with the official repository.


2555-2555: Confirm official VSCode extension repo link
The first asyncapi-preview entry’s repoUrl has been corrected to https://github.com/asyncapi/vs-asyncapi-preview. This matches the official extension repository.


2581-2581: Verify second VSCode extension entry
The second asyncapi-preview entry now points at https://github.com/Savio629/testing2, which looks like a placeholder or test repo. Please confirm this is intentional and replace with the correct extension repository if not.


3012-3012: Confirm official CLI repo link in "Others"
The AsyncAPI CLI entry under Others has been updated to https://github.com/asyncapi/cli, matching the official CLI.

config/tools-automated.json (19)

72-91: Metadata update for SIO-AsyncAPI looks good
Reordering the entry under Code-first tools and retaining its Python/Socket.IO/Flask metadata aligns correctly with its purpose.


94-113: Zod Sockets entry approved
The updated description, links, and filter categories (code-first, dsl, framework) accurately reflect the tool’s capabilities.


116-135: AsyncAPI.NET (ByteBardOrg) entry approved
C#/.NET filters and converter/validator tags are correctly applied.


180-203: Verify cross-listing of ZenWave SDK
This tool now appears across multiple categories (Code Generators, DSL, CLIs, Mocking and Testing). Confirm that intentional duplication aligns with the site's taxonomy.

Would you like a shell script to list all occurrences of ZenWave SDK in both configuration files?


225-243: AsyncAPI Modelina metadata approved
Filters, ownership flag, and categorization (code-generator) are correct.


399-423: DSL category entries approved
Both ZenWave SDK and Zod Sockets are valid domain-specific language tools and have appropriate tags.


443-465: Frameworks category entries approved
Glee and Zod Sockets are properly listed as framework-level tools.


531-554: Verify ZenWave SDK under Mocking and Testing
The SDK again appears here. Please ensure cross-listing is intentional and users can discover it sensibly.


557-577: Mokapi metadata approved
Go/Golang & CLI tags align with the tool’s functionality.


585-600: AsyncAPI Validation entry approved
TypeScript validator metadata is correct.


603-614: AsyncAPI.NET under Validators approved
Reusing the C#/.NET SDK for validation is acceptable given its filter tags.


714-737: Verify ZenWave SDK under CLIs
Again cross-listed. Confirm this duplication is intended and documented in the UI.


740-760: Mokapi under CLIs approved
CLI tags and description align.


763-779: AsyncAPI CLI fork metadata approved
Forked CLI entry is properly flagged with isAsyncAPIOwner: false.


831-843: asyncapi-preview (fork) metadata approved
Forked extension entry is properly flagged with isAsyncAPIOwner: false.


911-930: Java Spring Template metadata approved
Generator-template tags and links appear correct.


971-986: Node.js Multiprotocol Template approved
All fields match the intended template capabilities.


813-825:

Details

✅ Verification successful

asyncapi-preview (official) metadata approved
Official VSCode extension listing looks correct.

Ensure the repoUrl swap for asyncapi-preview is mirrored in the primary tools.json:


🏁 Script executed:

#!/bin/bash
echo "Automated config preview URLs:"
jq -r '.["IDE Extensions"].toolsList[] | select(.title=="asyncapi-preview") | .links.repoUrl' config/tools-automated.json
echo "Primary config preview URLs:"
jq -r '.["IDE Extensions"].toolsList[] | select(.title=="asyncapi-preview") | .links.repoUrl' config/tools.json

Length of output: 545


Configuration Verified: repoUrl Swap Mirrored
Both config/tools-automated.json and config/tools.json include the same updated repoUrl entries for asyncapi-preview:


695-711:

Details

✅ Verification successful

AsyncAPI CLI official metadata approved
Official CLI listing is accurate.

Please verify that the repoUrl for "AsyncAPI CLI" matches between config/tools-automated.json and config/tools.json:


🏁 Script executed:

#!/bin/bash
echo "Automated config:"
jq -r '.CLIs.toolsList[] | select(.title=="AsyncAPI CLI") | .links.repoUrl' config/tools-automated.json
echo "Primary config:"
jq -r '.CLIs.toolsList[] | select(.title=="AsyncAPI CLI") | .links.repoUrl' config/tools.json

Length of output: 431


Repository URLs are consistent across automated and primary configs
Both config/tools-automated.json and config/tools.json list identical repoUrl entries for “AsyncAPI CLI”:

No discrepancies found—ready to merge.

Comment on lines 53 to 91
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"websiteUrl": "https://www.npmjs.com/package/zod-sockets",
"repoUrl": "https://github.com/RobinTail/zod-sockets"
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "TypeScript",
"language": "Typescript",
"technology": [
"Node.js",
"TypeScript"
"NestJS"
],
"categories": [
"code-first",
"dsl",
"framework"
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
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

Inconsistent language casing for nestjs-asyncapi
The language field is set to "Typescript", while other entries use the "TypeScript" spelling. Please standardize the casing to "TypeScript" for consistency across the file.

--- a/config/tools-automated.json
+++ b/config/tools-automated.json
@@ -58,7 +58,7 @@
         "filters": {
-          "language": "Typescript",
+          "language": "TypeScript",
           "technology": [
             "Node.js",
             "NestJS"
📝 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": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"websiteUrl": "https://www.npmjs.com/package/zod-sockets",
"repoUrl": "https://github.com/RobinTail/zod-sockets"
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "TypeScript",
"language": "Typescript",
"technology": [
"Node.js",
"TypeScript"
"NestJS"
],
"categories": [
"code-first",
"dsl",
"framework"
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "TypeScript",
"technology": [
"Node.js",
"NestJS"
],
"categories": [
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
🤖 Prompt for AI Agents
In config/tools-automated.json between lines 53 and 69, the language field for
the nestjs-asyncapi entry is set to "Typescript" which is inconsistent with
other entries using "TypeScript". Change the value of the language field to
"TypeScript" to maintain consistent casing throughout the file.

@akshatnema akshatnema closed this Jun 14, 2025
@akshatnema akshatnema deleted the update-tools/regenerateTools branch June 14, 2025 17:37
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.

4 participants