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

fix(client): returning never types on selections when extension enabled #19587

Merged
merged 4 commits into from
Jun 7, 2023

Conversation

millsp
Copy link
Member

@millsp millsp commented Jun 3, 2023

closes #19572
closes #17767

Slack thread

@millsp millsp added this to the 4.16.0 milestone Jun 5, 2023
@millsp millsp marked this pull request as ready for review June 5, 2023 19:28
@millsp millsp requested a review from a team as a code owner June 5, 2023 19:28
@millsp millsp requested review from SevInf and Druue and removed request for a team June 5, 2023 19:28
Copy link
Contributor

@SevInf SevInf left a comment

Choose a reason for hiding this comment

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

So, I think I understood the problem and the fix and I think this is a way to go if we want to stay backward-compatible.
Question for Prisma 5 or the future: should {select: { relation: boolean }} give you out relation: SomeModel | undefined instead? Or we've decided that it would be too inconvenient even for the future?

@millsp millsp merged commit e52af84 into main Jun 7, 2023
68 of 69 checks passed
@millsp millsp deleted the fix/client/extension-never-type branch June 7, 2023 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants