420 telegram metric apis

[Behzad-rabiei]

Summary by CodeRabbit

• New Features
  • Enhanced community data retrieval by including createdAt and updatedAt fields in community queries.
• Chores
  • Updated dependency version for @togethercrew.dev/db from ^3.0.78 to ^3.0.79.

[coderabbitai]

Walkthrough

The pull request introduces two primary changes: a minor version update for the @togethercrew.dev/db dependency in package.json and an enhancement to the community.controller.ts file. The changes expand the data retrieval for community-related functions by including createdAt and updatedAt fields in the populate method, providing more comprehensive metadata about community objects.

Changes

File	Change Summary
package.json	Bumped @togethercrew.dev/db dependency from ^3.0.78 to ^3.0.79
src/controllers/community.controller.ts	Updated getCommunities and getCommunity functions to include createdAt and updatedAt fields in populate method

Possibly related PRs

• feat: add createdAt updatedAt to response of community #421: Similar modifications to the getCommunity function, including createdAt and updatedAt fields in the populate method

Poem

🐰 A Rabbit's Ode to Timestamps 🕰️

Metadata dancing, fields so bright,
Communities now shine with temporal might
From creation's dawn to updates' gleam
Our data tells a richer, fuller dream
Version bumped with a hoppy 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. We would love to hear your feedback on Discord.

---

📜 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 78e088d and 4334206.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/controllers/community.controller.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• package.json

🔇 Additional comments (2)

src/controllers/community.controller.ts (2)

25-25: Adding createdAt and updatedAt fields enhances data visibility.
This change is beneficial for traceability, as it makes it easier to track the lifecycle of each platform.

---

Line range hint 36-39: Ensure the createdAt and updatedAt fields are properly indexed.
Including timestamps in the populate call is great for data tracking. However, if these fields will be queried frequently (e.g., sorting or filtering by date), confirm that relevant indexes exist in the database to maintain query performance.

---

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

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.