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

merge dev to main (v2.11.2) #1957

Merged
merged 2 commits into from
Jan 13, 2025
Merged

merge dev to main (v2.11.2) #1957

merged 2 commits into from
Jan 13, 2025

Conversation

ymc9
Copy link
Member

@ymc9 ymc9 commented Jan 13, 2025

No description provided.

Copy link
Contributor

coderabbitai bot commented Jan 13, 2025

Warning

Rate limit exceeded

@ymc9 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 57 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cc3cd8c and 9a55cbc.

📒 Files selected for processing (1)
  • tests/regression/tests/issue-1955.test.ts (1 hunks)
📝 Walkthrough

Walkthrough

This pull request encompasses changes across multiple files, primarily focusing on version update and policy handling modifications. The main changes include updating the version to "2.11.2" in the JetBrains plugin build configuration, enhancing the createManyAndReturn method in the policy handler to improve result selection, and adding two new regression tests for PostgreSQL database schema validation using ZenStack.

Changes

File Change Summary
packages/ide/jetbrains/build.gradle.kts Version updated from "2.11.1" to "2.11.2"
packages/runtime/src/enhancements/node/policy/handler.ts Modified createManyAndReturn method to use makeIdSelection and explicitly set include to undefined
tests/integration/tests/enhancements/with-policy/create-many-and-return.test.ts Updated test assertions to check specific properties of created posts
tests/regression/tests/issue-1955.test.ts Added new test suite for PostgreSQL database schema validation

Sequence Diagram

sequenceDiagram
    participant PolicyHandler
    participant ModelClient
    participant PolicyUtils
    
    PolicyHandler->>PolicyUtils: makeIdSelection(model)
    PolicyUtils-->>PolicyHandler: return selected ID fields
    PolicyHandler->>ModelClient: createManyAndReturn(updatedArgs)
    ModelClient-->>PolicyHandler: return results with only ID fields
Loading

Possibly related PRs


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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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
Contributor

@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: 1

🧹 Nitpick comments (2)
tests/regression/tests/issue-1955.test.ts (2)

14-14: Fix typo in field name.

The field name 'expections' appears to be a typo of 'exceptions'.

-                expections String[]
+                exceptions String[]

Also applies to: 57-57


24-40: Enhance test coverage.

The test assertions could be more comprehensive:

  1. Verify the 'exceptions' field is present and correctly populated
  2. Add test cases for error scenarios
  3. Test the behavior when invalid data is provided

Example enhancement:

await expect(
    db.post.createManyAndReturn({
        data: [
            {
                name: 'bla',
                exceptions: ['error1'],
            },
            {
                name: 'blu',
                exceptions: ['error2'],
            },
        ],
    })
).resolves.toEqual(
    expect.arrayContaining([
        expect.objectContaining({ 
            name: 'bla',
            exceptions: ['error1'],
        }),
        expect.objectContaining({ 
            name: 'blu',
            exceptions: ['error2'],
        }),
    ])
);

// Add error case
await expect(
    db.post.createManyAndReturn({
        data: [
            {
                name: '',  // Invalid empty name
            },
        ],
    })
).rejects.toThrow();

Also applies to: 75-91

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b7d813 and cc3cd8c.

⛔ Files ignored due to path filters (13)
  • package.json is excluded by !**/*.json
  • packages/ide/jetbrains/package.json is excluded by !**/*.json
  • packages/language/package.json is excluded by !**/*.json
  • packages/misc/redwood/package.json is excluded by !**/*.json
  • packages/plugins/openapi/package.json is excluded by !**/*.json
  • packages/plugins/swr/package.json is excluded by !**/*.json
  • packages/plugins/tanstack-query/package.json is excluded by !**/*.json
  • packages/plugins/trpc/package.json is excluded by !**/*.json
  • packages/runtime/package.json is excluded by !**/*.json
  • packages/schema/package.json is excluded by !**/*.json
  • packages/sdk/package.json is excluded by !**/*.json
  • packages/server/package.json is excluded by !**/*.json
  • packages/testtools/package.json is excluded by !**/*.json
📒 Files selected for processing (4)
  • packages/ide/jetbrains/build.gradle.kts (1 hunks)
  • packages/runtime/src/enhancements/node/policy/handler.ts (1 hunks)
  • tests/integration/tests/enhancements/with-policy/create-many-and-return.test.ts (1 hunks)
  • tests/regression/tests/issue-1955.test.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/ide/jetbrains/build.gradle.kts
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: build-test (20.x)
  • GitHub Check: build-test (20.x)
  • GitHub Check: build-test (20.x)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: OSSAR-Scan
  • GitHub Check: dependency-review
  • GitHub Check: OSSAR-Scan
🔇 Additional comments (3)
tests/regression/tests/issue-1955.test.ts (1)

41-45: LGTM! Proper error handling and cleanup.

The try/finally blocks ensure proper cleanup of database resources, even if the test fails.

Also applies to: 92-96

tests/integration/tests/enhancements/with-policy/create-many-and-return.test.ts (1)

95-105: LGTM! Clear and precise test assertions.

The test clearly demonstrates the expected behavior:

  1. Successfully creates two posts
  2. Verifies that the title field is accessible only when published is true
  3. Confirms that both posts are created regardless of field-level access
packages/runtime/src/enhancements/node/policy/handler.ts (1)

481-488: LGTM! Improved field selection for policy checks.

The changes ensure that only ID fields are selected for return, which is essential for proper read-back checks. The explicit setting of include: undefined prevents unintended relation loading.

tests/regression/tests/issue-1955.test.ts Outdated Show resolved Hide resolved
@ymc9 ymc9 merged commit ba80eda into main Jan 13, 2025
11 checks passed
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