feat: Adding discourse analyzer config!

[amindadgar]

Summary by CodeRabbit

• New Features

  • Updated the tc-analyzer-lib package to version 1.4.0, indicating new functionalities or enhancements.
  • Introduced the DiscourseAnalyzerConfig class for enhanced analytics configuration specific to the Discourse platform.
  • Made DiscourseAnalyzerConfig available for external use alongside DiscordAnalyzerConfig.

• Bug Fixes

  • None.

• Documentation

  • None.

• Refactor

  • None.

• Style

  • None.

• Tests

  • None.

• Chores

  • None.

• Revert

  • None.

[coderabbitai]

Walkthrough

The update introduces significant enhancements to the tc-analyzer-lib package. The version has been incremented from 1.3.0 to 1.4.0, reflecting new features and improvements. A new class, DiscourseAnalyzerConfig, has been added to support analytics for the Discourse platform, expanding the library's capabilities. Additionally, this class integrates various user interaction analytics into the platform's configuration, alongside the existing Discord support.

Changes

Files	Change Summary
setup.py	Updated version from 1.3.0 to 1.4.0.
tc_analyzer_lib/schemas/platform_configs/init.py	Added import for DiscourseAnalyzerConfig alongside DiscordAnalyzerConfig.
tc_analyzer_lib/schemas/platform_configs/discourse.py	Introduced DiscourseAnalyzerConfig class for configuring analytics specific to the Discourse platform.

Poem

🐇 In the meadow where changes bloom,
A new config hops, dispelling gloom.
Discourse emerges, ready to play,
With analytics to brighten the day!
Version leaps, and features abound,
In the world of code, joy is found! 🥕✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d90888a and f1d593e.

Files selected for processing (3)

• setup.py (1 hunks)
• tc_analyzer_lib/schemas/platform_configs/init.py (1 hunks)
• tc_analyzer_lib/schemas/platform_configs/discourse.py (1 hunks)

Files skipped from review due to trivial changes (1)

• setup.py

Additional comments not posted (5)

tc_analyzer_lib/schemas/platform_configs/__init__.py (1)

3-3: Import statement looks good.

The import statement for DiscourseAnalyzerConfig is correctly added, making it available for external use.

tc_analyzer_lib/schemas/platform_configs/discourse.py (4)

11-13: Platform and resource identifier initialization looks good.

The platform is correctly set to "discourse" and the resource identifier to "category_id".

---

14-59: Hourly analytics initialization looks good.

The hourly analytics list is correctly populated with various HourlyAnalytics objects, each configured with appropriate properties.

---

61-80: Raw analytics initialization looks good.

The raw analytics list is correctly populated with various RawAnalytics objects, each configured with appropriate properties.

---

82-82: Super call looks good.

The super().__init__ call correctly passes the initialized parameters to the base class.