fix: wrong value of the enum in the tools-schema.json

[JeelRajodiya]

Description
Corrects the schema enum elements in

website/scripts/tools/tools-schema.json

Line 73 in 2e31739

"Rubby",

website/scripts/tools/tools-schema.json

Line 105 in 2e31739

"Rubby",

Related issue(s)
Closes #3282

Summary by CodeRabbit

• Bug Fixes
  • Corrected a typo from "Rubby" to "Ruby" in the programming language options of the AsyncAPI tool discovery schema.

This ensures accurate representation of programming languages for users interacting with the schema.

[coderabbitai]

Walkthrough

The pull request modifies the JSON schema for the AsyncAPI tool discovery file, specifically correcting a typo where "Rubby" has been changed to "Ruby" in the filters.language.anyOf and filters.language.items.anyOf sections. The structure of the schema remains intact, including properties like title, description, links, and filters. The changes ensure accurate representation of programming language options without altering the overall functionality or validation rules of the schema.

Changes

File Path	Change Summary
scripts/tools/tools-schema.json	Corrected typo from "Rubby" to "Ruby" in language filters.

Assessment against linked issues

Objective	Addressed	Explanation
Correct the enum value for Ruby (#3282)	✅

🐇 In the schema, a change so bright,
"Rubby" to "Ruby," now feels just right.
With filters in place, the structure stays,
Accurate options for coding ways!
Let's hop with joy, for the fix is here,
A clearer path for all, let’s give a cheer! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2e31739 and c4adc21.

📒 Files selected for processing (1)

• scripts/tools/tools-schema.json (2 hunks)

🧰 Additional context used

🔇 Additional comments (3)

scripts/tools/tools-schema.json (3)

73-73: Correct spelling change implemented.

The misspelling of "Ruby" has been successfully corrected in this enum. This change aligns with the PR objectives and maintains the integrity of the schema structure.

---

105-105: Correct spelling change implemented consistently.

The misspelling of "Ruby" has been successfully corrected in this enum as well. This change is consistent with the previous correction and maintains the schema's integrity.

---

Line range hint 1-231: Summary: Successful correction of "Ruby" spelling in schema.

The PR objectives have been fully met:

1. Both instances of "Rubby" have been corrected to "Ruby" in the filters.language enums.
2. The changes are consistent and maintain the schema's structure and validation rules.
3. No other instances of the misspelling were found in the file.

These corrections improve the accuracy of the AsyncAPI tool discovery schema without introducing any side effects or structural changes.

To ensure no instances of "Rubby" remain in the codebase, run the following command:

This command should return no results, confirming that all instances have been corrected.

✅ Verification successful

All instances of "Rubby" have been successfully corrected.

The verification process confirms that there are no remaining instances of "Rubby" in the codebase. All corrections meet the PR objectives, ensuring the accuracy and integrity of the tools-schema.json file.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining instances of "Rubby" in the codebase
rg --type json '"Rubby"'

Length of output: 26

---

Script:

#!/bin/bash
# Search for any remaining instances of "Rubby" in the entire codebase
rg '"Rubby"'

Length of output: 14

---

Script:

#!/bin/bash
# Perform a case-insensitive search for any remaining instances of "Rubby" in all text files
rg -i '"rubby"'

Length of output: 17

---

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

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	ef7af4b
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/6707fd3b3eddac00081655d1
😎 Deploy Preview	https://deploy-preview-3283--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.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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