Fix relation_fields validation to accept primary key indexes
#4376
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
yubrot
requested review from
jkomyno and
Druue
and removed request for
a team
|
|
Druue
approved these changes
Mar 18, 2024
CodSpeed Performance ReportMerging #4376 will not alter performanceComparing Summary
|
|
Hey, @yubrot this looks great, thank you so much for the contribution! |
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 resolves prisma/language-tools#1387.
The existing implementation did not take into account indexes by primary key. This has been corrected.
There is room for consideration that
indexes()may have to include primary keys, but this PR does not address that.