chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Added new language and technology tags, including ".NET", "Watermill", "Paho", and "RabbitMQ".
  • Introduced new API and tool entries such as "AsyncAPI Server API" and "nestjs-asyncapi".
  • Created new categories like "Code-first tools" and "GitHub Actions" for improved organization.

• Improvements

  • Reorganized and cleaned up tool categories for better clarity and navigation.
  • Updated and corrected metadata, including URLs, ownership flags, languages, and technology tags.
  • Removed duplicate and redundant entries across tags and tools for a more streamlined experience.

[coderabbitai]

Walkthrough

This update revises two JSON configuration files: config/all-tags.json and config/tools-automated.json. In all-tags.json, new language and technology tags are added, duplicate and redundant entries are removed, and the tag lists are cleaned up. In tools-automated.json, the structure and categorization of AsyncAPI tools are reorganized, with new categories, tools, and APIs introduced, duplicate entries removed, and metadata such as URLs, languages, and ownership flags corrected and updated throughout the file.

Changes

File(s)	Change Summary
config/all-tags.json	Added ".NET" to languages with color styling; added "Watermill," "Paho," and "RabbitMQ" to technologies; removed duplicate technology entries; cleaned up redundant tags; maintained consistent color schemes.
config/tools-automated.json	Reorganized tool categories and entries; added new API ("AsyncAPI Server API") and new category ("Code-first tools"); updated, renamed, and reordered tool entries; corrected URLs, languages, technology tags, and ownership flags; removed duplicates; merged and deduplicated converters; created new "GitHub Actions" category; updated templates and IDE extension metadata.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Website
    participant ConfigFiles

    User->>Website: Requests tools/tags data
    Website->>ConfigFiles: Reads all-tags.json and tools-automated.json
    ConfigFiles-->>Website: Returns updated tags and tool metadata
    Website-->>User: Displays updated tags and reorganized tools

Loading

Possibly related PRs

• chore: update tools.json #3857: Modifies config/all-tags.json and config/tools-automated.json, focusing on updating tags and tool entries, including additions, removals, and reorganization.
• chore: update tools.json #3274: Updates the same configuration files with changes to tags and tools metadata, indicating related configuration management.
• chore: update tools.json #3292: Modifies config/all-tags.json and config/tools-automated.json with updates to tags and tools, showing a direct connection in configuration updates.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

A hop, a skip, a bounding cheer,
New tags and tools have gathered here!
Duplicates gone, the list is clean,
With colors bright and tools unseen.
AsyncAPI’s garden grows anew—
🐇 config files, we thank you!
For every update, a carrot or two.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	0748467
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/6803a9239d8ea70008553ceb
😎 Deploy Preview	https://deploy-preview-4048--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 site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ab6340e) to head (0748467).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4048   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          671       671           
  Branches       115       115           
=========================================
  Hits           671       671           

☔ 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: 12

🔭 Outside diff range comments (1)

config/tools-automated.json (1)

949-964: 🛠️ Refactor suggestion

Reconsider listing CLIs in "Others"

The CLI tools are already under the "CLIs" category—duplicating them in "Others" may mislead users. Either remove these or reference the primary CLI category.

🧹 Nitpick comments (4)

config/tools-automated.json (4)

138-143: Differentiate ByteBard fork from official SDK

The second AsyncAPI.Net entry appears identical except for the ByteBard URL. Rename the title (e.g., "AsyncAPI.Net (ByteBard)") or add a note in the description to clarify it’s a separate fork.

---

201-224: Re-evaluate multi-category assignment for ZenWave SDK

The ZenWave SDK appears under "Code Generators" with categories including "mocking-and-testing" and "cli". Consider splitting into separate entries per functionality or refining the categories array to accurately reflect its primary role.

---

803-810: Consolidate VSCode preview extension forks

Multiple asyncapi-preview entries may confuse users. Consider merging forks into one listing with metadata for each variant.

---

967-983: Consolidate or remove redundant CLI entries in "Others"

As above, these forked CLI entries under "Others" are duplicates of the "CLIs" category. Please streamline the listing.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ab6340e and 0748467.

📒 Files selected for processing (2)

• config/all-tags.json (1 hunks)
• config/tools-automated.json (25 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (5)

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

🔇 Additional comments (13)

config/tools-automated.json (13)

49-52: Approve new "Code-first tools" category introduction

The "Code-first tools" category is introduced correctly with a clear description. The category key and its initial structure align with existing patterns.

---

94-104: Approve Zod Sockets entry

The Zod Sockets tool’s metadata (links, filters, categories) looks accurate and consistent with other entries. No changes needed.

---

118-121: Consolidate duplicate AsyncAPI.Net entries

Two separate AsyncAPI.Net listings under "Code-first tools" point to different organizations (LEGO vs. ByteBard). If both are maintained, differentiate them in the title or add an org field; otherwise, merge into one entry.

---

180-198: Approve AsyncAPI Modelina updates

The Modelina entry correctly sets isAsyncAPIOwner to true and updates its metadata. The technology filters (React JS, Docker) look reasonable.

---

450-464: Approve Glee framework addition

The new "Frameworks" category and the Glee entry are well-structured and properly tagged as isAsyncAPIOwner: true.

---

507-509: Approve new Mocking and Testing category

The "Mocking and Testing" category header is correctly introduced with a clear description.

---

584-592: Approve AsyncAPI Validation addition

The new AsyncAPI Validation tool is correctly added with proper filters and naming.

---

659-664: Approve change to isAsyncAPIOwner flag

Setting "isAsyncAPIOwner": false for jasyncapicmp accurately reflects non-official ownership.

---

672-688: Approve official CLI entry

The official AsyncAPI CLI listing and its updated ownership flag are correct.

---

691-697: Approve forked CLI entry

The forked CLI variant is properly marked with isAsyncAPIOwner: false and a distinct repoUrl.

---

767-773: Approve asyncapi-preview (official) entry

The VSCode extension entry is consistent with other IDE tools.

---

782-789: Approve jAsyncAPI - IDEA plugin updates

The IntelliJ plugin entry correctly sets isAsyncAPIOwner: true and updates its URLs.

---

925-933: Approve Node.js Websockets Template

The Node.js Websockets Template entry correctly uses "javascript" for language and aligns with other generator templates.

[coderabbitai]

⚠️ Potential issue

Remove duplicate technology tags and refine .NET styling

The technologies array contains duplicate entries for "AsyncAPI Generator", "VSCode", and "SmartPaste". Please deduplicate these to prevent redundant UI entries. Additionally, the new ".NET" language tag reuses Scala’s color scheme—consider assigning a unique color to distinguish it visually.

[coderabbitai]

🛠️ Refactor suggestion

Use consistent language tag for Go

The Golang AsyncAPI Code Generator entry uses "language": "golang", but all-tags.json defines Go as "Go/Golang". Update to "language": "Go/Golang" to align tags.

[coderabbitai]

⚠️ Potential issue

Normalize language casing and add missing URLs

In the nestjs-asyncapi entry:

• "language": "Typescript" should be "TypeScript" to match tag definitions.
• Consider adding websiteUrl and/or docsUrl alongside repoUrl for completeness.

[coderabbitai]

⚠️ Potential issue

Remove duplicate AsyncAPI.Net in Converters

The Converters category lists AsyncAPI.Net twice (LEGO and ByteBard). Consolidate or clarify similar to the Code-first category.

[coderabbitai]

⚠️ Potential issue

Correct the language filter for Java Template

The Java Template entry uses ["javascript"] under language. It should be ["Java"] to match the template’s purpose and tag definitions.

[coderabbitai]

⚠️ Potential issue

Unify GitHub Actions category naming

Two entries for "GitHub Action for Generator" use different category filters ("github-actions" vs. "github-action"). Standardize on one tag (e.g., "github-actions") for consistency.

[coderabbitai]

⚠️ Potential issue

Fix language filter in Java Spring Cloud Stream Template

Similarly, update the language from ["javascript"] to ["Java"] for this template.

[coderabbitai]

⚠️ Potential issue

Consolidate duplicate AsyncAPI Studio editor entries

There are two AsyncAPI Studio entries—one official and one pointing to Shurtu-gal/action-test-bed. Merge into a single entry or rename the forked variant to make the distinction clear.

[coderabbitai]

⚠️ Potential issue

Add missing language filter to the new API entry

The "AsyncAPI Server API" listing under "APIs" has technology and categories filters but lacks a "language" property. For consistency with other API entries (e.g., "language": "Python"), please include a language field (likely "TypeScript").

[coderabbitai]

⚠️ Potential issue

Fix language filter in Java Spring Template

The language array is set to ["javascript"]; please change it to ["Java"] (or include ["Java","JavaScript"] only if appropriate).