chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Enhanced technology tags with refreshed color schemes for Scala and added new tags for Watermill, Paho, and RabbitMQ.
  • Updated AsyncAPI tool listings with revised names, descriptions, language filters, and improved categorization for a clearer experience.

[coderabbitai]

Walkthrough

The changes consist of updates to two JSON configuration files. In all-tags.json, the Scala technology entry has new color values, and new technology entries (Watermill, Paho, and RabbitMQ) are added. In tools-automated.json, several AsyncAPI-related tool entries have been renamed, re-described, and re-categorized with updated links, language filters, and technology filters.

Changes

File	Change Summary
config/all-tags.json	Updated Scala entry with new color values; added new entries for "Watermill", "Paho", and "RabbitMQ" in the "technologies" section.
config/tools-automated.json	Renamed and re-described AsyncAPI tool entries (e.g., AsyncAPI.Net, SIO-AsyncAPI, Golang AsyncAPI Code Generator, Java Spring Template, etc.); updated links, language and technology filters, and categories.

Possibly related PRs

• chore: update tools.json #3512: Directly aligns with updates in all-tags.json by modifying the Scala entry and adding new technology metadata.
• chore: update tools.json #3474: Involves similar modifications to the "technologies" section, affecting color values and additions.
• chore: update tools.json #3661: Contains changes to the Scala entry in all-tags.json with updated color properties, matching the main PR adjustments.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I hop through JSON fields with delight,
New colors and names make the config bright.
Scala now shines in a brand new hue,
And Watermill, Paho, RabbitMQ join the crew.
My whiskers twitch with every updated line,
A rabbit's joy in each change so fine!

---

📜 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 e22853c and 6a8ac9c.

📒 Files selected for processing (2)

• config/all-tags.json (1 hunks)
• config/tools-automated.json (23 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 (14)

config/tools-automated.json (13)

95-200: Duplicate/Redundant entries in Code–first tools

There are two (or more) entries for “AsyncAPI.Net” (lines 95–115 and 117–137) and for “SIO–AsyncAPI” (lines 139–159 and 160–181). Please verify if the apparent duplication is intentional. If these entries represent different configurations (for example, from different authors or with slight differences) consider adding a distinguishing property or comment; otherwise, consolidating duplicates would improve maintainability.

---

265-307: Multiple AsyncAPI.Net entries with different sources

In the same section you can see entries at lines 265–285 and again at 287–307 that both list “AsyncAPI.Net” but now use URLs from the ByteBardOrg organization. Confirm that it is correct for your use case to list both the LEGO– and ByteBardOrg–sourced entries and that their intent is clear to users.

---

314-474: Duplicate entries in Code Generators

Within the Code Generators section there are duplicate entries for “Golang AsyncAPI Code Generator,” “ZenWave SDK,” “AsyncAPI Modelina,” and “asyncapi-python” (each appearing twice with almost identical details). Please verify these duplications are intentional (for instance, if the tool is meant to appear in multiple lists) or consider consolidating the duplicates.

---

481-567: Duplicate entries in Converters

There are duplicate “AsyncAPI.Net” entries in the Converters section (lines 481–501 and 502–567). If both entries come from distinct sources or configurations, please add clarification; otherwise, consolidating them would reduce redundancy.

---

581-657: AsyncAPI Studio – Missing description and duplicate items

The “AsyncAPI Studio” tool appears multiple times in the Editors section. Notably, two of the entries (lines 619–637 and 639–647) have a null description. Please verify whether a description should be provided and that the duplicate entries are desired.

---

702-756: Duplicate entries in DSL

The DSL category lists “ZenWave SDK” more than once. Please verify if these duplicates are intended (for example, if the tool serves multiple DSL roles) or if they should be consolidated.

---

1056-1184: Potential duplication in Validators

In the Validators section several entries – particularly for “AsyncAPI.Net” and “AsyncAPI Validation” – appear in duplicate. Please review whether these repeating items are needed or if they can be merged to avoid redundancy while ensuring full coverage.

---

1185-1264: Duplicates in Compare tools

Both “AsyncAPI Diff” and “jasyncapicmp” appear more than once in the Compare tools section. Please confirm that the duplicates are intentional (for example, if the same functionality is meant to be accessible in different contexts) or consider a consolidation.

---

1266-1398: Repetitions within the CLIs category

Multiple “AsyncAPI CLI” entries are present, with variations in the repository URL (official versus a fork from hkirat). If these represent different variants, consider labeling them (for example, “Official” vs. “Community Fork”) so that users can clearly distinguish between the options. Otherwise, consolidating duplicates might be beneficial.

---

1399-1439: Duplicate entries in Bundlers

“AsyncAPI Bundler” is listed twice in the Bundlers section. Please verify if the duplication is expected or if the extra entry should be removed.

---

1440-1558: Duplicates in IDE Extensions

The “asyncapi-preview” extension appears multiple times with identical configuration. Consolidating these entries would simplify the configuration unless they serve different purposes.

---

1559-1797: Multiple duplicate entries in AsyncAPI Generator Templates

Within the Generator Templates section several tools (including “Java Spring Template”, “Java Template”, “Node.js Websockets Template”, and “Node.js Multiprotocol Template”) occur more than once. Please verify that the same tool is meant to be listed multiple times (for example, to indicate compatibility with different setups) or consolidate duplicate entries to improve clarity.

---

1798-1878: Duplicate entries in Others

Multiple “AsyncAPI CLI” items appear again under Others. Please double–check that these duplicates are intentional. If they are meant to be cross–listed across categories, consider whether a single entry with multiple category tags might suffice.

config/all-tags.json (1)

1-1: Updated technology color definitions and new entries

The update changes the “Scala” entry’s color scheme (from “bg-[#57f281]”/“border-[#37f069]” to “bg-[#D7C7F2]”/“border-[#A387D2]”) and adds new technology entries for “Watermill,” “Paho,” and “RabbitMQ,” all using the same color values. These changes align with the broader reorganization seen in the tools configuration. Please confirm that the new colors match your design guidelines.

---

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 plan to trigger planning for file edits and PR creation.
• @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	6a8ac9c
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67f31e458cc34400082e2d86
😎 Deploy Preview	https://deploy-preview-4023--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 (e22853c) to head (6a8ac9c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4023   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

☔ 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.