Jason Kuhrt

Did you upgrade a version of a Prisma 2 component? This change has been there for a few weeks or more now I think.

@mattiasewers Understood, hope to see you back when some stable releases start being made :)

Hey @turboxx thanks, issue created, will try to close today https://github.com/prisma-labs/nexus-prisma/issues/591 About intentionality, it is an intentional change by Prisma 2 and to date `nexus-prisma` has been a passthrough on...

Users still having issues with this. E.g. https://prisma.slack.com/archives/CKQTGR6T0/p1584649633468700. I think its fair to expect Prisma ID fields to map to GraphQL ID types :) I'm going to re-open this as...

I agree we should do this, moving to `someday`.

Hit this issue on a zip coming from GitHub actions. Solution by @hubgit solved it for me. Thanks!

Downgrading this from bug to tests. The bug was fixed by #88

@lvauvillier Thanks for this proposal. This is quite interesting. So far I'm leaning toward `Model.$create.` and `Model.$update.`. @HendrikJan The first one should be doable somehow since its a new function...

@lvauvillier I don't care about the breaking changes aspect. I'd just like to get with the best API. The reason I felt that `$create` and `$update` were good is that...

Food for thought: ```ts .. ``` ```js const User = objectType({ name: User.$name, description: User.$description, definition(t) { t.field(User.id.read); t.field(User.createdAt.read); // generates a NonNull field t.field(User.name.read); // generates a NonNull field...