feat: Added hivemind payload schema!

[amindadgar]

Summary by CodeRabbit

• New Features

  • Introduced an enhanced query payload option that supports specifying whether to bypass non-relevant responses.

• Chores

  • Updated package dependencies to improve data validation capabilities.
  • Increased the release version to 1.1.0.

[coderabbitai]

Walkthrough

This pull request updates dependency and version configurations while introducing a new data model. The requirements.txt file now adds a pydantic dependency and adjusts the formatting of an existing dependency. The setup.py file reflects a package version bump from 1.0.0 to 1.1.0. In addition, a new class named HivemindQueryPayload has been added to the schema module to aid in validating query payloads with Pydantic.

Changes

File(s)	Change Summary
requirements.txt, setup.py	- requirements.txt: Added new dependency pydantic>=2.0.0, <3.0.0 and removed extra space before < in the temporalio dependency. - setup.py: Updated package version from 1.0.0 to 1.1.0.
tc_temporal_backend/.../hivemind.py	Added new class HivemindQueryPayload extending BaseModel, with attributes: community_id (required string), query (required string), and enable_answer_skipping (optional boolean, defaulting to False).

Poem

I'm a cheerful rabbit, hopping through the code,
New dependencies and version bumps lighten my humble load.
With Pydantic’s magic in a brand new class I see,
Query payloads now structured as neat as can be.
I nibble on fresh carrots, bug-free and so spry,
Celebrating clean updates as time hops by!
🥕🐇

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

tc_temporal_backend/schema/hivemind.py (2)

1-3: Remove extra blank line.

There's an unnecessary extra blank line after the imports.

 from pydantic import BaseModel, Field
 
-

---

9-15: Add space between sentences in the description.

The description is missing a space between sentences, which affects readability.

         description=(
             "skip answering questions with non-relevant retrieved information"
-            "having this, it could provide `None` for response and source_nodes"
+            " having this, it could provide `None` for response and source_nodes"
         ),

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd5c3b9 and ed4593b.

📒 Files selected for processing (3)

• requirements.txt (1 hunks)
• setup.py (1 hunks)
• tc_temporal_backend/schema/hivemind.py (1 hunks)

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

• setup.py

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ci / lint / Lint

🔇 Additional comments (3)

tc_temporal_backend/schema/hivemind.py (1)

4-8: LGTM! Well-structured schema with clear field descriptions.

The class is well-defined with appropriate field types and helpful descriptions. The use of Field(...) correctly marks the fields as required.

requirements.txt (2)

4-4: LGTM! Improved formatting.

The formatting change improves consistency.

---

5-5: LGTM! Appropriate version constraints.

The version range is well-chosen, ensuring compatibility with Pydantic v2 features while preventing potential breaking changes from v3.