merge dev to main (v2.17.2)

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update a Next.js API route example in the README to use the new app directory routing conventions and handler setup. The JetBrains IDE package build script version is incremented. In the schema enhancer plugin, logic is added to remove auxiliary delegate properties from generated Prisma client files using a new helper method.

Changes

File(s)	Change Summary
README.md	Updated Next.js API route example to use app directory routing, new handler import, refactored handler setup, and named HTTP method exports.
packages/ide/jetbrains/build.gradle.kts	Bumped version from 2.17.1 to 2.17.2.
packages/schema/src/plugins/enhancer/enhance/index.ts	Added logic to remove delegate_aux_* fields from generated Prisma client files; added helper method transformVariableStatementProps.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant NextAPIHandler
    participant getPrisma
    participant NextRequestHandler

    User->>NextAPIHandler: Sends HTTP request (GET/POST/PUT/PATCH/DELETE)
    NextAPIHandler->>getPrisma: Extract user from request, return enhanced Prisma client
    NextAPIHandler->>NextRequestHandler: Pass request and Prisma client
    NextRequestHandler-->>User: Responds to HTTP request

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15 minutes

Possibly related PRs

• chore: remove unused code #2194: Removes the transformVariableStatementProps method as unused, directly affecting the same code element added in this PR.
• chore: Improve performance for prisma-client generation #2177: Modifies internal Prisma client generation logic in the enhancer plugin, including adding the same helper method as in this PR.
• chore: bump version #2203: Updates the Next.js API route example to the new app directory conventions and refactors handler setup, directly related to the README changes in this PR.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1da7440 and 6d11737.

⛔ 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 (3)

• README.md (1 hunks)
• packages/ide/jetbrains/build.gradle.kts (1 hunks)
• packages/schema/src/plugins/enhancer/enhance/index.ts (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: dependency-review
• GitHub Check: build-test (20.x)
• GitHub Check: build-test (20.x)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: build-test (20.x)

🔇 Additional comments (7)

packages/ide/jetbrains/build.gradle.kts (1)

12-12: LGTM: Version bump for release.

The version update from "2.17.1" to "2.17.2" is consistent with the PR objectives for releasing v2.17.2.

packages/schema/src/plugins/enhancer/enhance/index.ts (3)

2-2: LGTM: Import addition for runtime assertions.

The invariant helper import is appropriately added to support the new transformVariableStatementProps method.

---

572-597: LGTM: Enhanced Prisma client processing with auxiliary field removal.

The integration of auxiliary delegate property removal in the new Prisma client generator is well-implemented. The code properly loads the source file, transforms variable statements to remove delegate_aux_* properties, and safely handles file operations with proper cleanup.

---

756-775: LGTM: Clean implementation of variable statement property transformation.

The new transformVariableStatementProps method effectively handles the removal of auxiliary delegate properties from variable initializers. The use of invariant for type assertion and the consistent approach with the existing transformVariableStatement method demonstrate good code consistency.

README.md (3)

93-93: LGTM: Updated to app directory routing convention.

The file path correctly reflects the new Next.js app directory structure with route handlers.

---

95-96: LGTM: Import updates for new server integration.

The imports correctly reflect the updated ZenStack server integration pattern with NextRequestHandler from @zenstackhq/server/next and the necessary NextRequest type.

---

104-112: LGTM: Handler setup follows modern patterns.

The refactored handler implementation properly:

• Uses the new getPrisma function signature accepting only req
• Correctly configures the handler with useAppDir: true
• Exports named HTTP method handlers instead of default export

This aligns with current Next.js app directory conventions.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @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.