LogLevel enum conflicts with built-in Prisma type

[MansurAliKoroglu]

Bug description

I created an enum called LogLevel and used in my model. Model's create type is different than LogLevel enum type. So, this:

  await prismaClient.log.create({
    data: {
      level: LogLevel.INFO
    }
  });

fails typescript with Type '"INFO"' is not assignable to type 'LogLevel'. Did you mean '"info"'?ts(2820)

---

When I change enum name to Level types are correct.

How to reproduce

1. Create minimal ts project with just index.ts
2. Install prisma and @prisma/client and init + create + migrate enum and model

enum LogLevel {
  INFO
  WARN
}

model Log {
  id    Int      @id @default(autoincrement())
  level LogLevel
}

4. Write code in index.ts

import { LogLevel, PrismaClient } from '@prisma/client'

(async () => {
  const prismaClient = new PrismaClient();

  await prismaClient.log.create({
    data: {
      level: LogLevel.INFO
    }
  });
})()

6. Try to build ts and see error Type '"INFO"' is not assignable to type 'LogLevel'. Did you mean '"info"'?ts(2820)
7. Optionally, remove migration, change enum's name to Level and migrate + generate again to see no error with Level.INFO now.

Expected behavior

Generated types should be correct regardless enum's name

Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

enum Level {
  INFO
  WARN
}

model Log {
  id    Int      @id @default(autoincrement())
  level Level
}

import { Level, PrismaClient } from '@prisma/client'

(async () => {
  const prismaClient = new PrismaClient();

  await prismaClient.log.create({
    data: {
      level: Level.INFO
    }
  });
})()

Environment & setup

• OS: Kubuntu 22.04, Kernel version: 5.15.0-76-generic (64-bit)
• Database: PostgreSQL
• Node.js version: 18.16.0

Prisma Version

prisma                  : 4.16.2
@prisma/client          : 4.16.2
Current platform        : debian-openssl-3.0.x
Query Engine (Node-API) : libquery-engine 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-3.0.x.so.node)
Migration Engine        : migration-engine-cli 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at node_modules/@prisma/engines/migration-engine-debian-openssl-3.0.x)
Format Wasm             : @prisma/prisma-fmt-wasm 4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Default Engines Hash    : 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Studio                  : 0.484.0

[Jolg42]

This looks like a type clash with the Prisma Client enum "LogLevel" to me.

So renaming your enum name is the current workaround until we fix this.

Note that you could keep the original name in the database if you need to like this

enum Level {
  INFO
  WARN
  @@map("LogLevel")
}

Related to #12469