Type error: Property 'role' does not exist on type {...}, implementing role base auth

[dorin-js]

Following role-based-login-strategy article, i ran into an issue:

//components/Auth.tsx:35:31
--
Type error: Property 'role' does not exist on type '{ name?: string; email?: string; image?: string; }'

Typescript is yelling on if (session && session.user.role === 'Admin') at .role property.
Anybody, how do i bypass this issue? I modified local node modules rules, but in production it still won't allow :(

[tuppers360]

I am also struggling with this :-( get the same issue as you.

The docs were updated a while ago I am wondering if there is an issue with this strategy since some updates?

[tuppers360]

As I say i am new to this but could you define an enum in the prisma file like:
enum Role { USER ADMIN }
to assign the above value to the db field then use that type in the def file above?

[dorin-js]

I am kinda new aswell into coding, half year, first project in Prisma.
In my prisma i have something like

enum Role {
  SimpleUser
  Moderator
  Admin
}

model User {
  id            String    @id @default(cuid())
  name          String?
  email         String?   @unique
  emailVerified DateTime?
  image         String?
  role          Role      @default(SimpleUser)
  accounts      Account[]
  sessions      Session[]
}

but u can't use the same enum outside as there is slightly different syntax, no comas in prisma.schema

in my tsx i have

enum Role {
  SimpleUser = 'SimpleUser',
  Moderator = 'Moderator',
  Admin = 'Admin',
}

[dorin-js]

that's how it appears in MySQL

[dorin-js]

if u make some changes in prisma.schema don't forget to npx prisma db push and npx prisma migrate to push changes to db and in local node_modules files, and restart your editor, as there is a weird glitch.

[tuppers360]

weird I removed the type Role line all works! Love this programming :-)

Just need to do some testing

Thanks for the help and the convo!

[sylvaincodes]

//You need to provide custom types for the auth().sessionClaims object, simply redeclare this interface in the global namespace and provide your own custom keys.

export {};

// Create a type for the roles
export type Roles = "admin" | "user";

declare global {
interface CustomJwtSessionClaims {
metadata: {
role?: Roles;
};
}
}