Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Apr 28, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Updated the order of entries in the tags and tools configuration files for improved consistency and accuracy.
    • Corrected and standardized metadata, descriptions, and links for various tools.
    • Fixed capitalization and formatting for language and technology tags.
    • Ensured accurate categorization and removed duplicate or misplaced entries.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 28, 2025

Walkthrough

This update reorganizes the contents of two configuration files: config/all-tags.json and config/tools-automated.json. In all-tags.json, the order of entries in the languages and technologies arrays was changed without altering any values or adding/removing entries. In tools-automated.json, tool entries were extensively reordered across categories, with corrections to metadata such as titles, descriptions, links, and tags for consistency and accuracy. No structural changes or code modifications were made; only the arrangement and metadata of existing configuration data were updated.

Changes

File(s) Change Summary
config/all-tags.json Reordered entries in the languages and technologies arrays; no additions, removals, or value changes.
config/tools-automated.json Reorganized tool entries across categories; corrected and swapped metadata (titles, descriptions, links, tags); normalized formatting.

Possibly related PRs

Suggested reviewers

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

Poem

In the garden of configs, neat rows now align,
Tags and tools reshuffled—a sequence divine.
No colors were changed, no entries were lost,
Just order restored, and metadata embossed.
With JSONs refreshed, the fields gently sway—
A rabbit’s small hop brings a tidier day!
🐇✨


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
🪧 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 generate sequence diagram to generate a sequence diagram of the changes in 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
Copy link

netlify bot commented Apr 28, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit d348314
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/680ece166eb19800082b9a83
😎 Deploy Preview https://deploy-preview-4072--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

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
Copy link

codecov bot commented Apr 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (eb4f966) to head (6f325f2).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4072   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          733       733           
  Branches       121       121           
=========================================
  Hits           733       733           

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

@netlify
Copy link

netlify bot commented Apr 28, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 6f325f2
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/680ece26033a01000883bf84
😎 Deploy Preview https://deploy-preview-4072--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🔭 Outside diff range comments (3)
config/tools-automated.json (3)

53-70: ⚠️ Potential issue

Align filter tags with all-tags.json standards
The nestjs-asyncapi entry uses "Typescript" and "NestJS", which don't match the cases in config/all-tags.json ("TypeScript" and "Nest Js") and will break tag-based filtering.
Apply this diff:

"language": "Typescript",
-"language": "Typescript",
+"language": "TypeScript",

"technology": [
-  "Node.js",
-  "NestJS"
+  "Node.js",
+  "Nest Js"
]

180-197: ⚠️ Potential issue

Fix language filter casing for asyncapi-python
The asyncapi-python entry uses "python" (lowercase) but config/all-tags.json defines "Python". Update as follows:

-filters": {
-  "language": "python",
+filters": {
+  "language": "Python",
   "technology": [
     "amqp"
   ],

220-243: ⚠️ Potential issue

Add missing CLI tag or align technology filters
The ZenWave SDK entry includes "CLI" in technology, but config/all-tags.json has no CLI tag. Either:

  1. Add a CLI entry in all-tags.json
  2. Replace with an existing tag
    Missing tag definitions will prevent proper filtering.
🧹 Nitpick comments (1)
config/tools-automated.json (1)

925-933: Improve filter casing for HTML Template
The filters.language field uses "javascript" lowercase. To match all-tags.json, update to "JavaScript". Optionally unify type:

-"language": [
-  "javascript"
-],
+"language": "JavaScript",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eb4f966 and 6f325f2.

📒 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 (9)
config/all-tags.json (1)

1-1: Approve reordering of tags
The updated ordering of languages and technologies preserves all entries, improves logical grouping, and introduces no duplicates or omissions.

config/tools-automated.json (8)

94-113: Approve Code-first Zod Sockets metadata
The Zod Sockets tool entry has accurate metadata, correct tags (TypeScript, Node.js), and consistent categories.


116-135: Approve Code-first AsyncAPI.Net (ByteBardOrg) metadata
The updated AsyncAPI.Net entry points to the correct ByteBardOrg repo and retains valid filters.


138-157: Approve Code-first SIO-AsyncAPI metadata
The SIO-AsyncAPI entry metadata is consistent and aligns with the intended filtering tags.


399-421: Approve DSL category Zod Sockets
The Zod Sockets entry under DSL retains accurate metadata and consistent filter tags.


584-603: Approve Validators AsyncAPI.Net (ByteBardOrg)
The swapped AsyncAPI.Net entry for ByteBardOrg in the Validators section has correct links and filters.


606-622: Approve Validators AsyncAPI Validation
The AsyncAPI Validation entry metadata and tags are correct and consistent.


629-646: Approve Compare tools jasyncapicmp
The jasyncapicmp entry has proper metadata, tags, and classifications.


649-665: Approve Compare tools AsyncAPI Diff
The AsyncAPI Diff entry is correctly updated with consistent filter tags and ownership.

Comment on lines +907 to +915
"title": "Node.js Websockets Template",
"description": "Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-template"
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
},
"filters": {
"language": [
"javascript"
],
"language": "javascript",
"technology": [
"Springboot",
"Maven",
"Gradle"
"Node.js"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Standardize language casing for Node.js Websockets Template
The filters.language uses "javascript" (lowercase). For consistency and correct filtering, use "JavaScript":

-"language": "javascript",
+"language": "JavaScript",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Node.js Websockets Template",
"description": "Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-template"
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
},
"filters": {
"language": [
"javascript"
],
"language": "javascript",
"technology": [
"Springboot",
"Maven",
"Gradle"
"Node.js"
"title": "Node.js Websockets Template",
"description": "Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.",
"links": {
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
},
"filters": {
- "language": "javascript",
+ "language": "JavaScript",
"technology": [
"Node.js"

Comment on lines +826 to +834
"title": "Java Spring Cloud Stream Template",
"description": "Java Spring Cloud Stream template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/html-template"
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
},
"filters": {
"language": "javascript",
"language": [
"javascript"
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Unify filter structure and casing for Java Spring Cloud Stream Template
This entry’s filters.language field is an array of "javascript" (lowercase), which is inconsistent with other entries and tag definitions ("JavaScript"). Decide on a single type (string vs array) and correct casing:

-"language": [
-  "javascript"
-],
+"language": ["JavaScript"],
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Java Spring Cloud Stream Template",
"description": "Java Spring Cloud Stream template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/html-template"
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
},
"filters": {
"language": "javascript",
"language": [
"javascript"
],
"title": "Java Spring Cloud Stream Template",
"description": "Java Spring Cloud Stream template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
},
"filters": {
"language": ["JavaScript"],

Comment on lines +847 to 855
"title": "Java Spring Template",
"description": "Java Spring template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
"repoUrl": "https://github.com/asyncapi/java-spring-template"
},
"filters": {
"language": [
"javascript"
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Unify filter structure and casing for Java Spring Template
The filters.language uses ["javascript"]. It should either be a string or match the case in all-tags.json ("JavaScript"). Apply:

-"language": [
-  "javascript"
-],
+"language": "JavaScript",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Java Spring Template",
"description": "Java Spring template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
"repoUrl": "https://github.com/asyncapi/java-spring-template"
},
"filters": {
"language": [
"javascript"
],
"filters": {
- "language": [
- "javascript"
- ],
+ "language": "JavaScript",

Comment on lines +869 to +877
"title": "Java Template",
"description": "Java template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
"repoUrl": "https://github.com/asyncapi/java-template"
},
"filters": {
"language": "javascript",
"language": [
"javascript"
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Correct language filter for Java Template
The Java Template mistakenly sets "javascript" under filters.language. It should be "Java" to match the template’s language:

-"language": [
-  "javascript"
-],
+"language": "Java",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Java Template",
"description": "Java template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
"repoUrl": "https://github.com/asyncapi/java-template"
},
"filters": {
"language": "javascript",
"language": [
"javascript"
],
"title": "Java Template",
"description": "Java template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-template"
},
"filters": {
- "language": [
- "javascript"
- ],
+ "language": "Java",

@asyncapi-bot asyncapi-bot merged commit 860edd8 into master Apr 28, 2025
22 of 23 checks passed
@asyncapi-bot asyncapi-bot deleted the update-tools/regenerateTools branch April 28, 2025 00:47
@coderabbitai coderabbitai bot mentioned this pull request May 12, 2025
This was referenced Jun 9, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants