fix(prisma): replace select with include for user relation query #12434
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
@mcorbelli is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
github-actions
bot
added
adapters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12434 +/- ##
=======================================
Coverage 39.38% 39.38%
=======================================
Files 194 194
Lines 30676 30676
Branches 1341 1341
=======================================
Hits 12081 12081
Misses 18595 18595 ☔ View full report in Codecov by Sentry. |
ndom91
approved these changes
Dec 29, 2024
|
When will it be included in the npm release? Is there a date yet? @ndom91 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where Prisma's
selectstatement was incorrectly used to query theuserrelation in theAccountmodel. Sinceselectis only applicable for scalar fields, this caused Prisma to throw an error:Unknown field 'user' for select statement on model 'Account'.The fix replaces
select: { user: true }withinclude: { user: true }, which correctly fetches theuserrelation and resolves the issue.