feat: enable hivemind module for telegram

[Behzad-rabiei]

Summary by CodeRabbit

• New Features
  • Introduced enhanced configuration validation for Telegram integration. This update ensures the proper handling of activation settings, leading to improved accuracy and consistency when using Telegram-related functionalities. Users will benefit from a more reliable system where settings are verified more robustly, contributing to an overall enhanced user experience across supported platforms.

[coderabbitai]

Walkthrough

The changes add a new validation function for Telegram metadata. A new function, hivemindTelegramMetadata, is introduced to define a Joi schema that validates an object with a boolean activated property. The hivemindOptions function is updated to include a new case for PlatformNames.Telegram, which uses this newly defined schema. Additionally, the import statements were reformatted into a single line without affecting functionality.

Changes

File	Changes Summary
src/validations/module.validation.ts	- Added new function hivemindTelegramMetadata to validate { activated: boolean } using a Joi schema. - Updated hivemindOptions to include a case for PlatformNames.Telegram. - Reformatted import statements into a single line.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Validator as hivemindOptions
    participant TelegramSchema as hivemindTelegramMetadata

    Client->>Validator: Request validation for Telegram metadata
    Validator-->>Client: Check platform (PlatformNames.Telegram)
    Validator->>TelegramSchema: Validate { activated: boolean }
    TelegramSchema-->>Validator: Return Joi schema result
    Validator-->>Client: Return validated response

Loading

Possibly related PRs

• feat: add activated field to modules metadata #439: Adjustments involving the activated property in validation logic, indicating a code-level connection with the changes introduced here.

Poem

I’m a little rabbit hopping through the code,
Found a Telegram twist on the validation road.
With a schema so neat for activated so true,
My validation garden has a brand new view.
Hoppin' through changes with a joyful mode!
🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0cc27f and 09ea038.

📒 Files selected for processing (1)

• src/validations/module.validation.ts (3 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

src/validations/module.validation.ts

[error] 131-131: Do not add then to an object.

(lint/suspicious/noThenProperty)

🔇 Additional comments (2)

src/validations/module.validation.ts (2)

83-87: LGTM: Telegram metadata validation schema implemented correctly.

The new hivemindTelegramMetadata function follows the established pattern for platform-specific metadata validation, similar to the GitHub implementation. The schema correctly validates an object with a single boolean activated property.

---

129-132: LGTM: Telegram platform correctly integrated into validation logic.

The Telegram platform support is properly integrated into the existing hivemindOptions function by adding a new case to the switch statement. This ensures Telegram metadata will be validated using the appropriate schema.

Note: The static analysis tool raised a warning about "Do not add then to an object", but this can be safely ignored as it's a false positive. The use of then is part of Joi's validation syntax for conditional validation and is used consistently throughout the file.

🧰 Tools

🪛 Biome (1.9.4)

[error] 131-131: Do not add then to an object.

(lint/suspicious/noThenProperty)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.