fix: updated to use telegram config!

[amindadgar]

Summary by CodeRabbit

• New Features

  • Enhanced ETL process for Telegram data with improved metadata extraction.
  • Introduced configuration management for the analyzer, allowing for customizable analysis behavior.

• Chores

  • Updated tc-analyzer-lib dependency version from 1.4.10 to 1.4.11.

[coderabbitai]

Walkthrough

The changes in this pull request focus on enhancing the ETL process for Telegram data within the telegram_analyzer_etl.py file. Key modifications include the introduction of configuration management through TelegramAnalyzerConfig, updates to the analyze_telegram function for simplified metadata access, and adjustments to the Analyzer class's analyze method to accept new parameters. Additionally, the version of the tc-analyzer-lib package has been updated in requirements.txt.

Changes

File	Change Summary
dags/telegram_analyzer_etl.py	- Added import for TelegramAnalyzerConfig. - Updated analyze_telegram method signature to include config and send_completed_message. - Simplified metadata retrieval from platform_data.
requirements.txt	- Updated tc-analyzer-lib version from 1.4.10 to 1.4.11.

Possibly related PRs

• fix: telegram analyzer dag dependency! #299: This PR modifies the analyze_telegram function in the same file (telegram_analyzer_etl.py) and includes changes to its method signature, which is directly related to the updates made in the main PR.

Poem

In the fields of code, I hop with glee,
Analyzing Telegram, oh so free!
With configs in hand and data so bright,
Our ETL process now takes flight!
From ten to eleven, we leap with cheer,
A better tomorrow is finally here! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8703847 and 6f87d61.

📒 Files selected for processing (1)

• dags/telegram_analyzer_etl.py (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• dags/telegram_analyzer_etl.py

---

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: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6549a9c and 8703847.

📒 Files selected for processing (2)

• dags/telegram_analyzer_etl.py (2 hunks)
• requirements.txt (1 hunks)

🧰 Additional context used

🔇 Additional comments (2)

dags/telegram_analyzer_etl.py (2)

15-15: Import TelegramAnalyzerConfig is appropriate

The addition of the import statement for TelegramAnalyzerConfig is necessary for the new configuration functionality.

---

209-209: Instantiation of Analyzer is acceptable

Creating an instance of Analyzer without parameters aligns with its current usage and seems appropriate.