Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add nested queries to match book + syntactic sugar #387

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

MartianGreed
Copy link
Collaborator

@MartianGreed MartianGreed commented Jan 29, 2025

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

    • Enhanced clause building functionality in Dojo Engine SDK
    • Added new utility functions for creating complex query clauses
    • Improved support for nested and composite query conditions
  • Improvements

    • Updated method signatures for more flexible clause composition
    • Added new interface and type definitions to support advanced querying
  • Testing

    • Expanded test suite for clause builder with complex composition scenarios
    • Added test cases to verify clause building usability

Copy link

coderabbitai bot commented Jan 29, 2025

Walkthrough

The pull request introduces a series of patches across multiple Dojo Engine packages, focusing on enhancing the ClauseBuilder functionality in the SDK. The changes primarily involve adding new utility functions for clause construction, updating method signatures, and introducing a new ClauseBuilderInterface. The modifications aim to improve the flexibility and expressiveness of clause building, with particular emphasis on supporting more complex query compositions and providing syntactic sugar for clause creation.

Changes

File Change Summary
packages/sdk/src/clauseBuilder.ts - Added ClauseBuilderInterface type
- Introduced new functions: KeysClause, MemberClause, AndComposeClause, OrComposeClause
- Updated method signatures for or and and methods
packages/sdk/src/__tests__/clauseBuilder.test.ts - Added new test cases for complex clause composition
- Expanded imports to include new clause-related utilities

Possibly related PRs

Suggested reviewers

  • ponderingdemocritus

Poem

🐰 In the realm of Dojo's code so bright,
Clauses dance with newfound might,
Builders weave their complex spell,
Where queries rise and logic dwells!
A rabbit's cheer for syntax sweet! 🧩

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
packages/sdk/src/clauseBuilder.ts (3)

35-49: Consider validating the arguments more strictly.
Currently, KeysClause doesn't check whether models and keys align or perform any additional validation. If there's a mismatch or invalid input, it may produce surprising behavior.


74-85: Correct the doc comment to match the method name.
The JSDoc says "Saves some keyboard strokes to get a Composite 'Or' Clause," but the function is AndComposeClause. Consider updating the documentation to accurately reference "And" instead of "Or."

- * Saves some keyboard strokes to get a Composite "Or" Clause
+ * Saves some keyboard strokes to get a Composite "And" Clause

87-97: Correct the doc comment to match the method name.
The JSDoc says "Saves some keyboard strokes to get a Composite 'And' Clause," but the function is OrComposeClause. Consider updating the documentation accordingly.

- * Saves some keyboard strokes to get a Composite "And" Clause
+ * Saves some keyboard strokes to get a Composite "Or" Clause
packages/sdk/src/__tests__/clauseBuilder.test.ts (1)

217-250: Extend test scenarios for complex composition.
This test reveals impressive support for nested logical clauses. Consider adding negative or edge-case tests (e.g., empty arrays, invalid operators) to strengthen reliability.

.changeset/selfish-poets-grab.md (1)

15-15: Revisit the wording to avoid confusion.
If referring to "matchbook" as a single noun, consider adjusting "match book" accordingly. Otherwise, if you’re referencing matching "the book," no change is needed.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~15-~15: The noun “matchbook” is normally spelled as one word.
Context: ...atch --- fix: Add nested query test to match book + syntactic sugar

(BOOK_COMPOUNDS)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4ebdb4c and d030ace.

📒 Files selected for processing (3)
  • .changeset/selfish-poets-grab.md (1 hunks)
  • packages/sdk/src/__tests__/clauseBuilder.test.ts (2 hunks)
  • packages/sdk/src/clauseBuilder.ts (3 hunks)
🧰 Additional context used
🪛 LanguageTool
.changeset/selfish-poets-grab.md

[uncategorized] ~15-~15: The noun “matchbook” is normally spelled as one word.
Context: ...atch --- fix: Add nested query test to match book + syntactic sugar

(BOOK_COMPOUNDS)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: check
🔇 Additional comments (7)
packages/sdk/src/clauseBuilder.ts (4)

11-13: Interface approach looks good!
The ClauseBuilderInterface cleanly enforces a uniform build() method across different clause builders.


51-72: Well-structured helper function.
MemberClause clearly delegates its logic to the where method, providing a concise and consistent way to build clauses. This is a nice abstraction.


174-174: Implementation overwrites orClauses.
This method looks correct for setting OR clauses. Take care if multiple calls to or() within the same composite are intended to accumulate clauses; this code replaces previously stored OR clauses.


179-179: Implementation overwrites andClauses.
This method sets AND clauses as expected. Similarly to or(), re-calling and() replaces previously stored clauses, so ensure that’s the desired behavior.

packages/sdk/src/__tests__/clauseBuilder.test.ts (3)

2-7: New imports extend test coverage.
Bringing in AndComposeClause, MemberClause, etc., ensures thorough testing of new clause builder functionalities.


251-312: Thorough verification of nested composites.
The deeply nested expect block accurately confirms the correctness of the composite structure.


313-359: Excellent demonstration of syntactic sugar.
This comparison between manual compositions and helper functions boosts readability and confirms feature parity.

@MartianGreed MartianGreed merged commit 750229a into main Jan 31, 2025
6 checks passed
@MartianGreed MartianGreed deleted the feat/experimental-update branch January 31, 2025 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant