chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated and reorganized tag listings for technologies to remove duplicates and improve consistency in tag appearance.
  • Cleaned up and reordered tool listings, removing duplicate entries, updating metadata, and improving the organization of categories and templates. No visible changes to application features or user interface.

[coderabbitai]

Walkthrough

This update modifies two JSON configuration files: config/all-tags.json and config/tools-automated.json. In all-tags.json, the technologies array is reordered, duplicate entries are removed, and a consistent color scheme is applied, while the languages array remains largely unchanged. In tools-automated.json, duplicate tool entries are removed, several tools are repositioned within their categories, and metadata for some tools is updated or corrected. No changes are made to the structure or schema of the files, and no code entities are affected.

Changes

File(s)	Change Summary
config/all-tags.json	Reordered and deduplicated the technologies array, applied a consistent color scheme, and left the languages array mostly unchanged. No schema changes.
config/tools-automated.json	Removed duplicate tool entries, repositioned several tools within their categories, updated metadata, and reordered templates. No schema changes.

Possibly related PRs

• chore: update tools.json #3779: Also updates config/all-tags.json, particularly the technologies array, with similar reordering and color adjustments.
• chore: update tools.json #4023: Modifies the technologies section in config/all-tags.json, including tag updates and color changes.
• chore: update tools.json #3336: Updates both config/all-tags.json and config/tools-automated.json with similar reorganizations and metadata changes.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

Hopping through configs with nimble delight,
I tidy the tags and set colors just right.
Tools in a row, no duplicates found,
Each entry is neat, all nicely renowned.
With JSON in order, my work here is done—
A rabbit’s small hop, but a win for everyone!
🐇✨

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	c8556bb
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/680593a3f18e4a0008e5dd4a
😎 Deploy Preview	https://deploy-preview-4052--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 (2808ab5) to head (c8556bb).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4052   +/-   ##
=========================================
  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: 2

🔭 Outside diff range comments (1)

config/tools-automated.json (1)

826-931: ⚠️ Potential issue

Standardize and correct filters.language in Generator Templates.

Multiple templates use "javascript" (sometimes as a string, sometimes as an array) even for Java-based templates. This inconsistency can break tooling that expects a single string or array of actual languages. In particular:

• Java templates should have "Java" or ["Java"]
• Spring templates should use "Java"
• Ensure uniform data type (string vs array) across all entries

Please correct these values and types to align with the rest of your configuration.

🧹 Nitpick comments (1)

config/tools-automated.json (1)

119-137: Normalize casing on the nestjs-asyncapi filters.

The "language" field is set to "Typescript" (lowercase “s”) whereas elsewhere you use "TypeScript". Please standardize the casing to maintain consistency with other entries.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2808ab5 and c8556bb.

📒 Files selected for processing (2)

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

config/tools-automated.json (4)

24-49: Verify removal of duplicate “SIO-AsyncAPI” from the “APIs” category.

The hunk shows changes around lines 24–49 in the APIs.toolsList. Ensure that “SIO-AsyncAPI” is intentionally retained here—if consolidating this tool under “Code‑first tools” only, remove it entirely from APIs.toolsList to avoid duplication.

---

205-226: Confirm metadata for “AsyncAPI Modelina” in Code Generators.

The “AsyncAPI Modelina” entry lists "React JS" and "Docker" as technologies, which may not reflect the actual stack of this tool. Please verify and correct the filters.technology array to accurately describe Modelina’s dependencies.

---

428-465: Ordering change for “Frameworks” looks good.

Swapping “Glee” to appear before “Zod Sockets” and updating its isAsyncAPIOwner flag is clear and intentional. The applied metadata appears consistent.

---

715-734: Review duplicate “AsyncAPI CLI” entries under “CLIs”.

There are two “AsyncAPI CLI” blocks (one with the official repo and one with the fork). If the fork is meant as a separate supported tool, consider renaming or adding a distinguishing field. Otherwise, consolidate or remove the redundant entry.

[coderabbitai]

⚠️ Potential issue

Remove residual duplicate tags in the technologies array.

I notice that several entries still appear more than once (e.g., “AsyncAPI Generator”, “VSCode”, “SmartPaste”). These duplicates will lead to redundant UI elements and confusion. Please deduplicate the list to ensure each technology appears only once.

[coderabbitai]

🛠️ Refactor suggestion

Eliminate the duplicate “SIO-AsyncAPI” entry under “Code-first tools”.

There are two identical SIO-AsyncAPI blocks in this list. Consolidate into a single entry or remove the redundant one to prevent confusion in your documentation.