Matt Kindy

Given the issue I described in https://github.com/MichalLytek/typegraphql-prisma/issues/10#issuecomment-1137308858, this seems like a good strategy to resolve it. I'm going to look into this futher

Just want to add more information to this thread since this is causing us problems at a very inopportune time -- I had this working in our project (under a...

I managed to transpile my code and use `node` directly. I set my `stack-size` option to 1200 for now, and that's enough to get past the error for now. I...

Yes, I still see this problem locally. Pretty significant problem if the whole point is to avoid writing invalid queries. I see this without using hooks -- just the raw...

I dug a bit into the generated code and noticed this section: ```ts export const Thunder = (fn: FetchFunction) => ( operation: O, graphqlOptions?: ThunderGraphQLOptions, ) => (o: Z |...

We also see this with this relationship ```prisma model QuoteBid { id String @default(cuid()) @id @db.VarChar(30) createdAt DateTime @default(now()) updatedAt DateTime @updatedAt ... pendingEditId String? @map("pendingEdit") @unique @db.VarChar(30) pendingEdit QuoteBidEdit?...

This is preventing us moving on to completing our Prisma 1 -> 2+ upgrade

Is there any estimate on when this might get looked at or patched?

@solumos thanks for that information! I'll look into that approach

I was using TypegraphQL Prisma at the time, so hard for me to give an exact log. It is easily replicated from the schema above, I would think. We followed...