You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description and expected behavior
The Clerk integration guide here specifies setting up the user model in the following way:
model User {
id String @id
@@ignore
}
This specifies using @@ignore which causes the User model to not be included in the Prisma client.
This however causes an issue with running zenstack generate as the Access Policy plugin cannot resolve the auth() model in policy rules (@@allow, @@deny )
The expected behaviour is to be able to use @@ignore, to avoid the User model in the prisma client. When we use Clerk we don't store the User information in the Db.
Screenshots
Environment (please complete the following information):
Description and expected behavior
The Clerk integration guide here specifies setting up the user model in the following way:
This specifies using
@@ignore
which causes the User model to not be included in the Prisma client.This however causes an issue with running
zenstack generate
as the Access Policy plugin cannot resolve theauth()
model in policy rules (@@allow
,@@deny
)The expected behaviour is to be able to use
@@ignore
, to avoid the User model in the prisma client. When we use Clerk we don't store the User information in the Db.Screenshots
Environment (please complete the following information):
Additional context
Discord Discussion Thread: https://discord.com/channels/1035538056146595961/1068743295863369858/1175510739495174275
The text was updated successfully, but these errors were encountered: