Jason Kuhrt
Jason Kuhrt
@sooxt98 I'll need some convincing for this because its a significantly different use-case than what nexus-prisma is trying to give you. I get the appeal at first but as an...
The con of this is that its a enum use-case served by a much larger and unrelated source of data. So many example where the fit is awkward. 1. Hovering...
> Using nexus-prisma generates code of name end of specified suffix, User_、Post_、UserWhereUniqueInput_、PostWhereUniqueInput_、UserWhereInput_ and PostWhereInput_, for avoiding conflict of name of GraphQLObjectType. This can be achieved with namespace importing ```ts import...
> Providing inputObjectType and objectType Function be expose. Please open an issue on Nexus about how to support this. I think it would be less confusing if the building blocks...
Maybe we need a new helper method. ```ts import { User } from 'nexus-prisma' export const UserObjectType = objectType({ name: 'User', definition(t) { t.field(User.id); t.field(User.name); }, }); export const SecretUserObjectType...
@nikolasburk with the Prisma 1:1 limitation [here](https://www.prisma.io/docs/concepts/components/prisma-schema/relations#the-side-without-a-relation-scalar-must-be-optional) it means that it is unsafe for Nexus Prisma to assume that both sides of the 1:1 relation will always be non-null, right?
@nikolasburk Thanks that's clear! While it might not be guarantee-able at the database level the user's application logic might guarantee it and thus at the API level at least they...
They are passing https://github.com/prisma/nexus-prisma/runs/2614915354#step:9:65?
No, it tests that the first build fails, then after reflection, passes. And it always logs because it's hard to debug when it fails without logs. So I just log...
I would like to consider this problem now as an incremental test/progress of forthcoming Nexus Prisma issues. This issue feels modest and shouldn't be too hard to implement. But doing...