chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Style
  • Refreshed the visual presentation of technology tags with a unified color palette for improved consistency.
• Refactor
  • Updated tool listings by revising names, descriptions, and links across API, code-first, validation, and template sections to enhance clarity and overall user experience.

[coderabbitai]

Walkthrough

This pull request updates two JSON configuration files. In config/all-tags.json, several color codes for languages and technologies have been updated to a uniform scheme. In config/tools-automated.json, tool entries across multiple sections have been renamed, re-described, and reorganized. The overall JSON structure remains unchanged with no modifications to exported entities.

Changes

File	Change Summary
config/all-tags.json	Updated color codes for multiple languages and technologies to bg-[#61d0f2] and border-[#40ccf7], maintaining the JSON structure.
config/tools-automated.json	Renamed and re-described tool entries in the "APIs", "Code-first tools", "Validators", and "AsyncAPI Generator Templates" sections, with some entries being swapped back.

Possibly related PRs

• chore: update tools.json #3404: Updated color codes in config/all-tags.json, reflecting similar visual changes.
• chore: update tools.json #3588: Modified the same configuration entries with uniform color updates.
• chore: update tools.json #3642: Altered visual representations in config/all-tags.json for several technologies.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I'm the coding bunny, hopping through the night,
Config files glowing in a uniform light.
Colors now sing in a rhythmic tone,
Renamed tools dance in a reorganized zone.
With whiskers twitching and a joyful cheer,
I celebrate each JSON update here!

---

📜 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 7e31bc3 and 95f49f6.

📒 Files selected for processing (2)

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

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

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

🔇 Additional comments (14)

config/all-tags.json (1)

1-1: Uniform Color Scheme Update
The updated JSON now uses a consistent color scheme (using bg-[#61d0f2] with border-[#40ccf7]) for several language and technology entries. This update appears intentional for unified branding. Please verify that these new colors meet contrast and accessibility standards as defined in our design guidelines.

config/tools-automated.json (13)

6-11: APIs Section – Renamed Tool Update
The entry in the APIs section is now titled "AsyncAPI Server API" with an updated description and new link URLs. Ensure that these changes align with our official branding and that the updated URLs are correct and current.

---

25-45: APIs Section – SIO-AsyncAPI Reinstatement
This object reverts the tool name to "SIO-AsyncAPI" and restores its original description and repository links. Please confirm that this reversion is intentional and that it remains consistent with our overall tool categorization.

---

52-72: Code-first Tools – “Zod Sockets” Update
The first tool in the Code-first tools section is now renamed to "Zod Sockets" with a new descriptive text and updated links. Verify that this naming and description accurately summarize its Socket.IO validation functionality and that the filters (e.g. language: TypeScript, technology: Node.js and TypeScript) are correct.

---

97-116: Code-first Tools – “AsyncAPI.Net” Reversion
This object now reintroduces "AsyncAPI.Net" with its original description and links for the .NET SDK. It appears there has been a swap between "Zod Sockets" and "AsyncAPI.Net" entries. Please double-check that this swap is intentional and that the two tool entries remain distinct without causing duplication or confusion.

---

426-441: GitHub Actions – Generator Tool Update
The "GitHub Action for Generator" entry now features an updated title, description, and a repository URL that now points to the CLI repository. Additionally, the category has been adjusted to "github-actions". Confirm that these changes accurately reflect the tool’s purpose and that the link points to the correct resource.

---

443-458: GitHub Actions – CLI Tool Update
The "GitHub Action for CLI" now has a revamped title and description along with updated repository links and refined technology filters. These updates enhance clarity regarding its features. Please verify that all the details correctly describe the tool’s capabilities.

---

516-532: Validators Section – AsyncAPI Validation Update
The "AsyncAPI Validation" tool now shows an updated title, description, and repository link. Its filters (using TypeScript and Node.js) are appropriate for a message validation package. The update appears straightforward and in line with our intended functionality.

---

533-554: Validators Section – AsyncAPI.Net Reversion
This tool entry reintroduces "AsyncAPI.Net" with the original .NET SDK description and links. Since the Validators category now contains both "AsyncAPI Validation" and "AsyncAPI.Net", please verify that having these similar entries will not cause redundancy or confusion in the categorization.

---

721-726: Generator Templates – HTML Template Update
The "HTML Template" now has an updated description that emphasizes its use for generating static documentation (using the AsyncAPI React component) along with an updated repository link. This improvement aligns with our documentation strategy.

---

739-755: Generator Templates – Node.js Multiprotocol Template Update
The "Node.js Multiprotocol Template" now includes a detailed description that highlights its multi-protocol server generation capabilities along with revised repository links. Ensure that the description fully captures its intended use case and that the link is correct.

---

757-776: Generator Templates – Java Spring Cloud Stream Template Update
The tool has been renamed to "Java Spring Cloud Stream Template" with a concise description and new repository URL. However, note that the language filter is set to ["javascript"] even though the template is Java-based. Please verify if this filter is correct or if it should be updated to reflect Java.

---

778-794: Generator Templates – Node.js Websockets Template Update
The "Node.js Websockets Template" now features an updated title, description, and repository link. The changes maintain consistency within this category.

---

796-814: Generator Templates – Java Template Update
The "Java Template" entry now includes an updated description and repository link. However, similar to the previous template, the language filter remains set to ["javascript"]. Please review this setting to ensure it correctly reflects the target language for this Java-based template.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (7e31bc3) to head (95f49f6).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3661   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          732       732           
=========================================
  Hits           732       732           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	95f49f6
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67a949942c20c10008d07a36
😎 Deploy Preview	https://deploy-preview-3661--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.