-
-
Notifications
You must be signed in to change notification settings - Fork 724
[TRI-5172] Fix Prisma 6.6+ compatibility #2036
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
[TRI-5172] Fix Prisma 6.6+ compatibility #2036
Conversation
Co-Authored-By: Eric Allam <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Co-Authored-By: Eric Allam <[email protected]>
|
Co-Authored-By: Eric Allam <[email protected]>
Co-Authored-By: Eric Allam <[email protected]>
Fix Prisma 6.6+ Compatibility
This PR addresses issue #1926 (TRI-5172) by adding the
--schema
flag to the Prisma CLI command for schema folders. In Prisma 6.6.0+, they require anoutput
path and no longer generate the Prisma client innode_modules
, making the--schema
flag mandatory.Changes
--schema=./prisma/schema
flag to the Prisma CLI command for schema folders in theprismaExtension
Testing
This change has been tested with both Prisma 5.0.0 and Prisma 6.6.0+ in separate test environments to verify compatibility:
--schema
flag works correctly with the default node_modules output location--schema
flag works correctly with custom output pathsBoth tests confirm that the
prismaExtension
works correctly with the--schema
flag for schema folders across Prisma versions.Link to Devin run
https://app.devin.ai/sessions/efafead475da4805947ca060e0aa0a88
Requested by
Eric Allam ([email protected])