Skip to content
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

Check for Primary Key Name for UniqueWhereInput #214

Closed
wants to merge 4 commits into from

Conversation

jpulec
Copy link

@jpulec jpulec commented May 6, 2022

closes #213

I think something like this should do it.

@vercel
Copy link

vercel bot commented May 6, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
nexus-prisma ✅ Ready (Inspect) Visit Preview May 6, 2022 at 9:49PM (UTC)

Copy link
Member

@jasonkuhrt jasonkuhrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add some test coverage for this? Thanks!

@jpulec
Copy link
Author

jpulec commented Nov 7, 2022

@jasonkuhrt I just modified one of the existing tests to use a custom primary key name. Hope that's kinda what you're looking for.

@jpulec
Copy link
Author

jpulec commented Apr 16, 2023

Closing as this doesn't seem to be actively matina

@jpulec jpulec closed this Apr 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Resolver Generated for Non-Scalar Fields Does Not Reflect name From Prisma Schema for Primary Keys
2 participants