Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update tools.json #3474

Merged
merged 1 commit into from
Dec 16, 2024
Merged

chore: update tools.json #3474

merged 1 commit into from
Dec 16, 2024

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Dec 16, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added "AsyncAPI CLI" to the technologies list.
    • Introduced "Zod Sockets" in both "Code-first tools" and "DSL" categories.
  • Updates

    • Updated color and borderColor attributes for multiple technology entries to a uniform style.
    • Renamed and reorganized various tools in the "GitHub Actions" and "AsyncAPI Generator Templates" sections for clarity.

Copy link

coderabbitai bot commented Dec 16, 2024

Walkthrough

The pull request introduces modifications to two configuration files: config/all-tags.json and config/tools-automated.json. In all-tags.json, a new technology "AsyncAPI CLI" is added, and several existing technology entries have their color attributes standardized to a uniform blue-like palette. The tools-automated.json file sees reorganization of tools, including the addition of "Zod Sockets", renaming of GitHub Actions, and updates to AsyncAPI Generator Templates with shifts in technology focus.

Changes

File Changes
config/all-tags.json - Added "AsyncAPI CLI" technology
- Updated color scheme for multiple technologies to bg-[#61d0f2] and border-[#40ccf7]
config/tools-automated.json - Added "Zod Sockets" to Code-first tools and DSL categories
- Swapped titles and descriptions of GitHub Actions
- Renamed and updated AsyncAPI Generator Templates

Suggested labels

autoapproved, autoupdate

Poem

🐰 A Rabbit's Config Dance

Tags and tools, a colorful array,
Blue hues dancing in a playful display,
AsyncAPI CLI joins the scene,
Zod Sockets leaping, so serene!
Configuration magic, neat and bright,
A techno-rabbit's pure delight! 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.


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

Copy link

netlify bot commented Dec 16, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 0c84b3b
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/675f7656a816a8000843777d
😎 Deploy Preview https://deploy-preview-3474--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

codecov bot commented Dec 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.59%. Comparing base (a32888b) to head (0c84b3b).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3474   +/-   ##
=======================================
  Coverage   86.59%   86.59%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          575      575           
  Misses         89       89           

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

Copy link

@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: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a32888b and 0c84b3b.

📒 Files selected for processing (2)
  • config/all-tags.json (1 hunks)
  • config/tools-automated.json (12 hunks)
🔇 Additional comments (2)
config/all-tags.json (1)

1-1: LGTM! Color standardization improves visual consistency

The changes standardize the color scheme for multiple technology entries while maintaining proper JSON structure. The addition of AsyncAPI CLI follows the established pattern.

config/tools-automated.json (1)

74-95: LGTM! Appropriate multi-category placement for Zod Sockets

The tool is correctly added to relevant categories with consistent information across entries.

Also applies to: 292-313

Comment on lines +763 to +765
"language": [
"javascript"
],
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix incorrect language specifications in templates

Several Java-based templates incorrectly specify "javascript" as their language. Additionally, there's inconsistent usage of string vs array for the language field.

Apply these corrections:

  "filters": {
    "language": [
-     "javascript"
+     "java"
    ],

Also applies to: 784-786, 806-808

Comment on lines +584 to +602
{
"title": "AsyncAPI CLI",
"description": "One CLI to rule them all. \nThis is a CLI that aims to integrate all AsyncAPI tools that you need while AsyncAPI document development and maintainance. \nYou can use it to generate docs or code, validate AsyncAPI document and event create new documents.\n",
"links": {
"websiteUrl": "https://www.asyncapi.com/tools/cli",
"repoUrl": "https://github.com/asyncapi/cli"
},
"filters": {
"technology": [
"TypeScript"
],
"categories": [
"others",
"cli"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
}
},
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Consolidate duplicate AsyncAPI CLI entries

There are duplicate entries for AsyncAPI CLI pointing to different repositories (official and fork). This could cause confusion for users.

Consider:

  1. Removing the fork entry if it's not officially supported
  2. Clearly indicating in the description if the fork serves a different purpose

Also applies to: 847-874

Comment on lines +390 to 439
"title": "GitHub Action for CLI",
"description": "GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone",
"links": {
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
"repoUrl": "https://github.com/asyncapi/github-action-for-cli"
},
"filters": {
"technology": [
"AsyncAPI Generator"
"AsyncAPI CLI"
],
"categories": [
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for CLI",
"description": "GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone",
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"links": {
"repoUrl": "https://github.com/asyncapi/github-action-for-cli"
"repoUrl": "https://github.com/asyncapi/cli"
},
"filters": {
"technology": [
"AsyncAPI CLI"
"AsyncAPI Generator"
],
"categories": [
"github-action"
"github-actions"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"description": null,
"links": {
"repoUrl": "https://github.com/asyncapi/cli"
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-actions"
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
"isAsyncAPIOwner": false
}
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix inconsistent category naming in GitHub Actions

The category name varies between "github-action" and "github-actions". This should be standardized to ensure consistent filtering.

Standardize to "github-action" across all entries:

  "categories": [
-   "github-actions"
+   "github-action"
  ],
📝 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": "GitHub Action for CLI",
"description": "GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone",
"links": {
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
"repoUrl": "https://github.com/asyncapi/github-action-for-cli"
},
"filters": {
"technology": [
"AsyncAPI Generator"
"AsyncAPI CLI"
],
"categories": [
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for CLI",
"description": "GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone",
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"links": {
"repoUrl": "https://github.com/asyncapi/github-action-for-cli"
"repoUrl": "https://github.com/asyncapi/cli"
},
"filters": {
"technology": [
"AsyncAPI CLI"
"AsyncAPI Generator"
],
"categories": [
"github-action"
"github-actions"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"description": null,
"links": {
"repoUrl": "https://github.com/asyncapi/cli"
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-actions"
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
"isAsyncAPIOwner": false
}
}
"title": "GitHub Action for CLI",
"description": "GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone",
"links": {
"repoUrl": "https://github.com/asyncapi/github-action-for-cli"
},
"filters": {
"technology": [
"AsyncAPI CLI"
],
"categories": [
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"links": {
"repoUrl": "https://github.com/asyncapi/cli"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
}
},
{
"title": "GitHub Action for Generator",
"description": null,
"links": {
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
}

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot asyncapi-bot merged commit 11d46e4 into master Dec 16, 2024
34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-tools/regenerateTools branch December 16, 2024 00:42
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.

2 participants