Fix field parsing in require-field-index#799
Merged
Merged
Conversation
f90c3d4 to
dfdcccf
Compare
dfdcccf to
392267d
Compare
maxh
approved these changes
Jan 14, 2026
maxh
left a comment
Collaborator
There was a problem hiding this comment.
thanks! i'll get this out shortly
Collaborator
|
@pedro try https://github.com/loop-payments/prisma-lint/releases/tag/v0.13.1 and lmk if any further issues! |
Contributor
Author
|
Working nicely, thank you! |
This file contains hidden or 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
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.
Hi folks, thanks for this project!
Quick fix here - in my app
require-field-indexis throwing an error on models that have@@uniquewith a name followed by fields defined in an array, like:which results in:
So adding a test and fixing the field parsing there.