Prisma generates enums as string while NestJS GraphQL generates as real enum.

Problem

enums are scalar types in Prisma & generated like this;

export const Continent: {
  Asia: 'Asia',
  Europe: 'Europe',
  America: 'America',
  Africa: 'Africa'
};

export type Continent = (typeof Continent)[keyof typeof Continent]

However, for instance in Nestjs GraphQL, the same enum is generated as enum like this;

export enum Continent {
    Asia = "Asia",
    Europe = "Europe",
    America = "America",
    Africa = "Africa",
    Australia = "Australia"
}

As a result, these two Continents are not assignable, Prisma one is string, GraphQL one is enum. This causes problems is resolvers when we return them.

Suggested solution

In my opinion, Prisma should create enums as a real enum! At least, we sould be able to overwrite the default enum generation in Prisma. (If it’s not already available. I hope it is!)

[kokokenada]

Same issue here. Maybe prisma could also generate an Enum* form to keep everyone happy and maintain compatibility. E.g. add export EnumContinent { … Alternatively nestjs could update registerEnumType to also take the const form that prisma generates. Until then, I can’t seem to find any work around except for duplicating the definition in enum form.

[jeckvld]

have exactly the same issue!