-
-
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
Fix(JSON): Allow JSON types to be skipped through Prisma.skip #2064
Conversation
📝 WalkthroughWalkthroughThe changes update the logic in the Changes
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🔇 Additional comments (1)
✨ Finishing Touches
🪧 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 (
|
9ed71b1
to
87b0128
Compare
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.
Good catch @diesal11 ! Thanks for making the fix. I'm merging it and will publish a new release.
Another JSON edge case!
When the
strictUndefinedChecks
Prisma Preview feature is enabled,Prisma.skip
is required to be used overundefined
. The types generated for@Json
fields misses this typing in cases where the field is optional in the Prisma type, for example withinUpdateInput
typesNote this doesn't allow using
Prisma.skip
on a field within the JSON type, as that doesn't appear to be supported by Prisma.