chore: update tools.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Added new HTML language support to the registry.
  • Updated tool metadata including descriptions, repository links, ownership flags, and categorization across multiple tools and sections for consistency and accuracy.
  • Reorganized tool entries and improved data structure across various categories.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Configuration files updated to add a new HTML language tag and extensively reorganize tool entries across tools metadata files. Changes include adding an HTML language entry to the tags configuration, and restructuring multiple tool definitions with renamed entries, swapped metadata (titles, descriptions, links), and adjusted categorizations across multiple tool categories.

Changes

Cohort / File(s)	Summary
Language Tags config/all-tags.json	Added new HTML entry with name: "HTML", color: "bg-[#61d0f2]", and borderColor: "border-[#40ccf7]" to the languages array; increased HTML item count from 2 to 3.
Tools Metadata & Entries config/tools-automated.json	Extensively reorganized tool entries across multiple sections (APIs, Code-first tools, DSL, Code Generators, Editors, Frameworks/Converters/Documentation). Changes include: removed websiteUrl from AsyncAPI Server API links; swapped/renamed entries (AsyncAPI.NET ↔ nestjs-asyncapi, SIO-AsyncAPI); relocated tools between sections; adjusted language/technology/categories (e.g., TypeScript/Node.js ↔ C#/.NET); toggled isAsyncAPIOwner flags; added/removed entries (asyncapi-python, Zod Sockets, Node.js Multiprotocol Template, HTML Template, Java Spring Cloud Stream Template); swapped description texts between null and descriptive content; corrected/swapped repository URLs across multiple tool blocks.
Tools Configuration config/tools.json	Removed websiteUrl from AsyncAPI Server API tool links. Swapped descriptions and repository URLs between AsyncAPI Studio editor entries (asyncapi/studio ↔ fork-based repo); adjusted third Studio entry description and repoUrl. Added/updated HTML Template entries under Code Generators section with description and repoUrl changes; reassigned description fields between concrete text and null values; swapped HTML Template repository sources (dipaksodani/async-gen, WSOL12/html-template, asyncapi/html-template).

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

• config/tools-automated.json: Primary concern—extensive heterogeneous changes with multiple conflicting renames and cross-references between tool entries (AsyncAPI.NET ↔ nestjs-asyncapi, ZenWave SDK, Specmatic, Zod Sockets) scattered across different sections. Semantic inconsistencies noted in summary (tools appearing under different sections with altered ownership indicators). Each renamed/swapped entry requires individual verification of correctness.
• config/tools.json: Secondary concern—localized but interconnected swaps affecting AsyncAPI Studio entries and HTML Template metadata; repository URL reassignments require traceability verification.
• config/all-tags.json: Minimal effort (straightforward data addition); serves as foundation reference for tools changes.

Possibly related PRs

• chore: update tools.json #4117: Overlapping edits to config/all-tags.json (HTML tag addition) and config/tools.json (HTML Template entry)—directly related at file/entity level.
• chore: update tools.json #4399: Modifies same config files with overlapping changes to tool metadata swaps and editor entries (AsyncAPI Studio, tool reorganization).
• chore: update tools.json #4230: Modifies all three config files with overlapping edits to HTML template/tool records and tooling metadata entries.

Suggested reviewers

• derberg
• anshgoyalevil
• akshatnema
• sambhavgupta0705

Poem

🐰 Hopping through configs with a whisker's delight,
New HTML tags and tools rearranged just right,
AsyncAPI juggled, Studios swapped with care,
Templates reshuffled through the digital air!
Order from chaos, a metadata dance—
Our toolbox evolves with each clever advance! 🎭

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update tools.json' is vague and does not convey meaningful information about the changeset. While it mentions one file, it fails to summarize the actual changes, which involve significant and concerning alterations across multiple configuration files including duplicate entries, inconsistent renames, swapped URLs, and semantic inconsistencies.	Provide a more descriptive title that summarizes the key changes, such as 'chore: consolidate and reorganize tools configuration across multiple files' or break the changes into more focused, descriptive commits with specific titles.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-tools/regenerateTools

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	d13dedb
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/6923a9e034decd0009fcf8f7
😎 Deploy Preview	https://deploy-preview-4639--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 project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (33db13d) to head (d13dedb).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4639   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          799       799           
  Branches       146       146           
=========================================
  Hits           799       799           

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

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	33
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-4639--asyncapi-website.netlify.app/

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)

config/tools.json (1)

2804-2884: Multiple HTML Template entries with identical titles and mixed official/community repositories.

The AsyncAPI Generator Templates section contains three "HTML Template" entries (lines 2804–2830, 2832–2857, 2859–2884) pointing to different repositories:

1. github.com/asyncapi/html-template (official) – description provided
2. github.com/WSOL12/html-template (community fork) – description null
3. github.com/dipaksodani/async-gen (community fork) – description null

All three share identical titles and filters (JavaScript, HTML, generator-template), so users cannot distinguish them in the UI. This creates confusion about which is the recommended/official template.

Recommend either:

• Removing community forks and keeping only the official template
• Renaming fork entries to clarify their status (e.g., "HTML Template (Community)")
• Adding descriptive text to distinguish them

config/tools-automated.json (2)

326-382: Duplicate AsyncAPI Studio entries with mixed official and community repositories (mirrors tools.json issue).

Like the issue flagged in tools.json, tools-automated.json contains three "AsyncAPI Studio" entries in the Editors section (lines 328–382) with:

1. Line 328–344: repoUrl: TahaShahid203/async-api-issue (fork), description: null, isAsyncAPIOwner: false
2. Line 346–363: repoUrl: asyncapi/studio (official), description: "Visually design your AsyncAPI files...", isAsyncAPIOwner: true
3. Line 365–382: repoUrl: Shurtu-gal/action-test-bed (test), description: null, isAsyncAPIOwner: false

Same concern as flagged in tools.json: mixing official AsyncAPI repos with personal forks/test repos in a public tools catalog.

---

996-1068: Multiple HTML Template entries with identical titles (tools-automated.json mirrors tools.json issue).

Lines 996–1068 contain three "HTML Template" entries pointing to different repositories:

1. Lines 996–1011: github.com/asyncapi/html-template (official), description: "HTML template for AsyncAPI Generator...", isAsyncAPIOwner: true
2. Lines 1014–1029: github.com/WSOL12/html-template (community fork), description: null, isAsyncAPIOwner: false
3. Lines 1032–1048: github.com/dipaksodani/async-gen (community fork), description: null, isAsyncAPIOwner: false

This mirrors the duplication issue in tools.json. All three entries share identical titles and filters, making them indistinguishable in the UI.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 33db13d and d13dedb.

📒 Files selected for processing (3)

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

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-01-19T04:51:41.255Z

Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3557
File: tests/fixtures/markdown/check-edit-links-data.js:3-11
Timestamp: 2025-01-19T04:51:41.255Z
Learning: In the AsyncAPI website repository, the test data in `tests/fixtures/markdown/check-edit-links-data.js` intentionally includes inconsistent paths (with and without 'docs' prefix) to verify the script's ability to normalize and handle ambiguous path structures.

Applied to files:

• config/tools.json
• config/tools-automated.json

📚 Learning: 2025-01-14T14:58:38.076Z

Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3557
File: tests/markdown/check-edit-links.test.js:20-46
Timestamp: 2025-01-14T14:58:38.076Z
Learning: In the AsyncAPI website codebase, the edit-page-config.json contains a fallback match entry that ensures determineEditLink function always has a valid target.value, making null checks unnecessary.

Applied to files:

• config/tools.json

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• 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: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI
• GitHub Check: cypress-run

🔇 Additional comments (2)

config/tools.json (1)

23-27: Removed websiteUrl from AsyncAPI Server API links.

Line 26 removes the websiteUrl field from the AsyncAPI Server API links object. If this URL was previously serving users as an entry point to the API documentation, this change reduces discoverability. The docsUrl field remains (line 26), but a separate websiteUrl may have had different content/purpose.

Please verify:

• Was the removal intentional or accidental?
• Does docsUrl provide sufficient alternative access?
• Are there user-facing impacts from this URL removal?

config/tools-automated.json (1)

225-243: Added asyncapi-python tool with incomplete metadata.

A new asyncapi-python tool is added to the Code Generators section (lines 225–243):

• description: "Easily generate type-safe and async Python applications from AsyncAPI 3 specifications."
• technology: only ["amqp"] is listed
• isAsyncAPIOwner: false

The technology filter is narrow (only AMQP) compared to other generators which list multiple target protocols. Please verify if this accurately represents the tool's capabilities or if the technology list should be expanded (e.g., Kafka, NATS, etc.).

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Duplicate HTML entry with generic styling in technologies array.

A new HTML entry is added to the technologies array using generic blue colors (#61d0f2, #40ccf7) that are shared with ~50+ other technology entries. However, the existing HTML entry in the languages array uses distinct orange colors (#E2A291, #E44D26). Additionally, lines 301–309 already contain two other HTML entries in technologies, creating duplication.

This appears to be unintentional data duplication or a bulk placeholder update. Please verify:

• Whether HTML should appear as a technology (distinct from the language-level HTML tag)
• Whether the generic blue color is intentional or if a semantic color should be chosen
• Whether the duplicate HTML entries should be deduplicated

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

AsyncAPI.Net and AsyncAPI.NET entries create potential confusion with similar names.

Lines 52–72 add "AsyncAPI.Net" (with lowercase 'et'), while lines 115–135 contain "AsyncAPI.NET" (with uppercase 'ET'). Both point to different repositories:

• AsyncAPI.Net: LEGO/AsyncAPI.NET (official LEGO fork)
• AsyncAPI.NET: ByteBardOrg/AsyncAPI.NET (community fork)

The name similarity combined with different repositories and ownership flags (isAsyncAPIOwner: false for both) may confuse users about which is the "official" .NET SDK. Recommend clarifying naming or descriptions to distinguish them clearly.

Also applies to: 115-135

---

🏁 Script executed:

#!/bin/bash
# Extract both AsyncAPI.Net entries to verify the review comment
echo "=== Lines 52-72 (AsyncAPI.Net) ==="
sed -n '52,72p' config/tools-automated.json

echo ""
echo "=== Lines 115-135 (AsyncAPI.NET) ==="
sed -n '115,135p' config/tools-automated.json

# Also check for all entries with "AsyncAPI" in the name to see full context
echo ""
echo "=== All AsyncAPI entries (titles only) ==="
rg -n '"title":\s*"AsyncAPI' config/tools-automated.json -A 0

Length of output: 326

---

🏁 Script executed:

#!/bin/bash
# Extract both AsyncAPI.Net entries to verify the review comment
echo "=== Lines 52-72 (AsyncAPI.Net) ==="
sed -n '52,72p' config/tools-automated.json

echo ""
echo "=== Lines 115-135 (AsyncAPI.NET) ==="
sed -n '115,135p' config/tools-automated.json

# Also check for all entries with "AsyncAPI" in the name to see full context
echo ""
echo "=== All AsyncAPI entries (titles and repos) ==="
rg -n '"title":\s*"AsyncAPI|"repoUrl"' config/tools-automated.json -A 0

Length of output: 5834

---

Review comment is valid but can be more precise about existing differentiation.

The naming concern is confirmed: both entries differ only by capitalization (AsyncAPI.Net vs AsyncAPI.NET) with different repositories (LEGO/AsyncAPI.NET vs ByteBardOrg/AsyncAPI.NET). However, the ByteBardOrg entry already includes a clarifying description: "The officially maintained fork," which helps differentiate it.

The issue is compounded by duplication across the file—these tools appear again at lines 250/272 (C# section), 608/648 (CLI/tools section), and 648/652 (validation section), where the same naming ambiguity repeats.

While the descriptions provide some mitigation, relying on capitalization alone to distinguish two similar tools is fragile and increases the risk of confusion, especially given the duplication. Consider updating the "AsyncAPI.Net" title to be more descriptive (e.g., "AsyncAPI.Net (LEGO)") or revising descriptions to be more explicit about which is recommended.

🤖 Prompt for AI Agents

In config/tools-automated.json around lines 52-72 (and the duplicate occurrences
at ~250/272, ~608/648, ~648/652), the two entries differ only by capitalization
causing ambiguity between repositories; update the titles and/or descriptions to
include the GitHub owner for clarity (e.g., change "AsyncAPI.Net" to
"AsyncAPI.Net (LEGO)" and the other to "AsyncAPI.NET (ByteBardOrg)"), and revise
each entry's description to explicitly state which repo maintains it (e.g.,
"maintained by LEGO" vs "officially maintained fork by ByteBardOrg"); apply the
same naming/descriptive changes consistently to all duplicated entries so users
can easily distinguish the two projects.