only difference is graphqlgen makes my grouped res...
# orm-help
c
only difference is graphqlgen makes my grouped resolver object types and
prisma-client
does not
k
Hey Callan, please try to keep longer discussions in a single thread. This helps us keep different discussions going on at the same time. 🙂
c
Sorry about that!
So in a picture, here's the implications of the types not matching
I'm often having to cast to unknown then to the desired value
simply because of this:
would really appreciate help or being told if I'm doing something wrong!
c
Callan any update on that topic? I faced the same problem
Someone faced that problem with wrong optional field type? (using bindings and graphqlgen) It can’t be that hard to resolve 😛
It’s related with https://github.com/prisma/prisma-binding/issues/188 But the same problem is using new prisma-client