fix: support in operator

[MartianGreed]

Closes #

Introduced changes

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Add a dedicated CI job for new examples
• Performed self-review of the code

Summary by CodeRabbit

• New Features
  • Added support for $in and $nin query operators
  • Introduced new query methods in() and notIn() for more flexible querying
  • Enhanced SDK query capabilities with advanced filtering options

[coderabbitai]

Walkthrough

The pull request introduces support for $in and $nin query operators in the SDK's query building functionality. This enhancement allows developers to create more complex queries by specifying inclusion and exclusion conditions for specific fields. The changes are implemented across two files: convertQuerytoClause.ts and queryBuilder.ts, adding new methods to the QueryEntity class and updating the operator conversion logic.

Changes

File	Change Summary
packages/sdk/src/convertQuerytoClause.ts	Added support for converting $in and $nin operators to corresponding Torii comparison operators
packages/sdk/src/queryBuilder.ts	- Added in() and notIn() methods to QueryEntity class - Updated Operator enum with in and nin values

Poem

🐰 Hop, hop, query's new delight!
In and NotIn, taking flight
SDK's magic now unfurled
Searching data, constraints twirled
Rabbit's code, a playful might! 🔍

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.

---

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 (1)

packages/sdk/src/queryBuilder.ts (1)

150-155: Double-check consistency of $nin usage.
The method notIn provides an exclusion-based filter. Similar to in, ensure it's clear that value should be an array to reduce confusion.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 33821e5 and b9cb6be.

📒 Files selected for processing (2)

• packages/sdk/src/convertQuerytoClause.ts (1 hunks)
• packages/sdk/src/queryBuilder.ts (2 hunks)

🔇 Additional comments (3)

packages/sdk/src/queryBuilder.ts (2)

143-148: Ensure value is correctly typed for $in operations.
While the logic matches the intended functionality, $in queries typically expect an array or similar iterable. Consider runtime validation or more specific typing to help users avoid passing non-iterable values.

---

194-195: Enumerations for $in and $nin are a welcome addition.
Expanding the Operator enum to include $in and $nin is aligned with standard query semantics. Good job!

packages/sdk/src/convertQuerytoClause.ts (1)

316-319: Mappings for $in and $nin appear correct.
The Torii "In" / "NotIn" mapping is logical and completes the integration. Confirm that downstream logic handles these operators as expected (e.g., checking for arrays).