[BUG] Types generated when using `@default(auth().id)` are not compatible with third party libraryes about zenstack HOT 2 CLOSED

Hi @nahtnam , thanks for filing this.

I checked the code and it seems next-admin has a hard-coded dependency to @prisma/client and doesn't allow customize its typing. Have you tried casting the enhanced prismaclient back to PrismaClient type and see if it works?

When using auth() in @default(), the only difference between zenstack-enhanced client and the original client's typing is the optionality of that field. It probably won't makes a real difference I suppose.

from zenstack.

Awesome, that seemed to do the trick! Do you know if there will ever be a case in the future where the change is not so type safe? Where type casting might cause issues?

In this case it's totally fine like you said because the types that the next-admin library uses is stricter

from zenstack.