-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Use prisma edge client for edge target #2060
Conversation
📝 WalkthroughWalkthroughThe pull request updates the Changes
Sequence Diagram(s)sequenceDiagram
participant G as Generate
participant S as createSimplePrismaImports
participant L as createLogicalPrismaImports
participant C as Conditional Logic
G->>S: Call with prismaImport and target
S->>C: Evaluate target parameter
C-->>S: Return corresponding import path
S-->>G: Return simple import string
G->>L: Call with prismaImport, prismaClientImport, and target
L->>C: Evaluate target parameter
C-->>L: Return corresponding logical import path
L-->>G: Return logical import string
Possibly related issues
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (3)
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fredevery , thank you for making the fix. The change looks good to me. I'll merge when CI passes.
While attempting to run a zenstack instance in a dockerized cloudflare enviroment, errors were thrown as the prisma client attempted to require node apis that aren't available in the cloudflare enviroment.
I was able to resolve this by forcing the zenstack edge enhancer to use the prisma edge client.