chore: Adjust JSON schema

[nickdnk]

Correctly define channel overrides

Reason for This PR

Correcting JSON schema

Description of Changes

Invalid nesting of custom channel logging options
Missing minProperties for root

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.

PR Checklist

[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

• All commits in this PR are signed (git commit -s).
• The reason for this PR is clearly provided (issue no. or explanation).
• The description of changes is clear and encompassing.
• Any required documentation changes (code and docs) are included in this PR.
• Any user-facing changes are mentioned in CHANGELOG.md.
• All added/changed functionality is tested.

Summary by CodeRabbit

• New Features
  • Enhanced configuration structure for the Logger plugin, requiring at least one property in the configuration object.
  • Introduced a detailed object structure for logging options under channels, improving clarity and customization.
• Bug Fixes
  • Enforced stricter validation rules to prevent extraneous properties in the Logger plugin's configuration.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the schema.json file for the Logger plugin. Key changes include the addition of a minProperties constraint at the root level, ensuring at least one property is present. The channels property has been restructured into a more detailed object format, which now requires a minimum of one property and includes specific logging options encapsulated within a properties object. The additionalProperties constraint remains false for both the root and channels objects to prevent extraneous entries.

Changes

File	Change Summary
schema.json	Added minProperties: 1 to the root object; restructured channels to include a description, type, additionalProperties: false, minProperties: 1, and encapsulated logging options within a properties object.

Poem

In the realm of logs, where data flows,
A structure refined, as clarity grows.
With channels defined, and rules set in place,
Our Logger now dances, with elegance and grace.
One property needed, to start the delight,
In the world of plugins, everything feels right! 🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

schema.json (1)

38-63: LGTM: Channel configuration restructuring

The restructuring properly nests logging options within the properties object and adds appropriate constraints. This fixes the invalid nesting issue while maintaining strict validation.

Consider enhancing the description to list common plugin names that users might configure, for example:

-          "description": "Custom logging options for the plugin specified as this object's key.",
+          "description": "Custom logging options for the plugin specified as this object's key. Common plugins include 'http', 'jobs', 'grpc', etc.",

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 9cc19f4 and 38b1a94.

📒 Files selected for processing (1)

• schema.json (2 hunks)

🔇 Additional comments (1)

schema.json (1)

7-7: LGTM: Root level validation enhancement

The addition of minProperties: 1 ensures that configurations cannot be empty, which is a valid constraint as the logger requires at least some configuration to be useful.