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

chore: Use queryBuilder for count op #31328

Merged
merged 1 commit into from Mar 2, 2024
Merged

Conversation

sharat87
Copy link
Member

@sharat87 sharat87 commented Feb 28, 2024

Summary by CodeRabbit

  • Refactor
    • Improved the efficiency of counting documents by datasource ID in the server's database interactions.

@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Feb 28, 2024
@sharat87 sharat87 marked this pull request as ready for review February 29, 2024 06:50
Copy link
Contributor

coderabbitai bot commented Feb 29, 2024

Walkthrough

Walkthrough

The update involves refining the way a MongoDB query is constructed and executed within a specific Java class. Instead of manually creating a query for counting documents based on a datasource ID, the code now leverages a queryBuilder() method. This method streamlines the process of setting up query criteria, enhancing code readability and maintainability.

Changes

File Path Change Summary
.../appsmith-server/src/.../CustomNewActionRepositoryCEImpl.java Updated countByDatasourceId method to use queryBuilder() for query criteria setup and document counting in MongoDB.

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>.
    • Generate unit-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@@ -351,12 +350,9 @@ public Mono<Long> countByDatasourceId(String datasourceId) {
where(NewAction.Fields.publishedAction + ".datasource._id").is(new ObjectId(datasourceId));

Criteria datasourceCriteria =
notDeleted().orOperator(unpublishedDatasourceCriteria, publishedDatasourceCriteria);
new Criteria().orOperator(unpublishedDatasourceCriteria, publishedDatasourceCriteria);
Copy link
Contributor

Choose a reason for hiding this comment

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

Whatever happened to the notDeleted clause? 🤔

Copy link
Member Author

Choose a reason for hiding this comment

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

Down the call-stack. it always gets added by the queryBuilder API. It's not optional today, notDeleted is always included in all calls of the queryBuilder API.

Here's the line that does this:

@sharat87 sharat87 requested a review from nidhi-nair March 1, 2024 03:25
@sharat87 sharat87 merged commit 76de676 into release Mar 2, 2024
19 checks passed
@sharat87 sharat87 deleted the chore/no-mongo-ops-2 branch March 2, 2024 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog Adding this label to a PR prevents it from being listed in the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants