466 turn offon all module

[Behzad-rabiei]

Summary by CodeRabbit

• New Features

  • Introduced an "activated" status for modules, now required on creation and available for updates on select module types.

• Chores

  • Upgraded the database dependency for improved performance.
  • Removed extraneous logging to streamline application behavior.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the migration tracking by modifying the .migrate file to reference a new migration file with an updated timestamp. It removes an obsolete migration script and adds a new migration script that adds an "activated" field to modules in the database. Additionally, the dependency version for @togethercrew.dev/db is updated in package.json. Debug logging statements and unused imports have been removed from several controller and service files. Lastly, the module validation schema now requires an activated field upon creation and includes it optionally during module updates.

Changes

Files	Change Summary
.migrate, src/migrations/db/1738072787796-update-user-documents-for-telegram-login.ts, src/migrations/db/1738072787797-add-activated-field-to-modules.ts	Updated migration tracking info in .migrate (lastRun, title, timestamp); removed the obsolete migration script; added a new migration script to add the activated field to modules.
package.json	Updated dependency version for @togethercrew.dev/db from ^3.3.0 to ^3.4.0.
src/controllers/hivemind.controller.ts, src/services/platform.service.ts, src/services/module.service.ts	Removed debug logging statements and unused imports, streamlining output in controller and service files.
src/validations/module.validation.ts	Added a new required activated boolean field in the module creation schema and an optional activated field in the update logic for specific module types (Hivemind, ViolationDetection, DynamicNft).

Sequence Diagram(s)

sequenceDiagram
    participant M as Migration Runner
    participant DB as Database
    M->>DB: Connect and execute new migration script
    DB-->>M: Update Module collection (set activated = true)
    M->>M: Log the number of modified modules & update .migrate tracking info
    M->>DB: Close the database connection

Loading

Possibly related PRs

• feat: enable hivemind module for telegram #468: Addresses the activated field validation in the Hivemind module, aligning with the new validation schema changes.
• feat: add activated field to modules metadata #439: Introduces the activated property in multiple module validation schemas, complementing the modifications in this PR.

Poem

Hi there, I'm your coding rabbit, on a joyful hop today,
Migration paths have shifted in a most organized way.
Debug logs are now but a whisper in the wind,
New fields bloom and let our modules begin.
With a twitch of my nose, I celebrate each fresh code ray!
🐇✨

---

📜 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 45b7e2d and dd03190.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (8)

• .migrate (1 hunks)
• package.json (1 hunks)
• src/controllers/hivemind.controller.ts (0 hunks)
• src/migrations/db/1738072787796-update-user-documents-for-telegram-login.ts (0 hunks)
• src/migrations/db/1738072787797-add-activated-field-to-modules.ts (1 hunks)
• src/services/module.service.ts (2 hunks)
• src/services/platform.service.ts (0 hunks)
• src/validations/module.validation.ts (3 hunks)

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