Table and column name mapping bug

Hi, I’ve encountered a weird bug with how I’m using mappings and prisma-erd-generator. Everything in Prisma generates the way I’d expect but prisma-erd-generator generates a svg for me with names I’m not expecting. Here’s some example that recreates the issue: prisma.schema:

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

generator erd {
  provider = "prisma-erd-generator"
  output = "./erd.svg"
  theme = "default"
}

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

model Store {
  @@map("stores")

  id                String            @map("store_id") @id @default(uuid())

  employees         Employee[]
  customers         Customer[]
}

model Employee {
  @@map("employees")

  id                String            @map("employee_id") @id @default(uuid())
  storeId           String            @map("store_id")

  store             Store             @relation(fields: [storeId], references: [id])
  orders            Order[]
}

model Customer {
  @@map("customers")

  id                String            @map("customer_id") @id @default(uuid())
  storeId           String            @map("store_id")

  store             Store             @relation(fields: [storeId], references: [id])
  orders            Order[]
}

model Order {
  @@map("orders")

  id                String            @map("order_id") @id @default(uuid()) 
  employeeId        String            @map("employee_id")
  customerId        String            @map("customer_id")

  employee          Employee          @relation(fields: [employeeId], references: [id])
  customer          Customer          @relation(fields: [customerId], references: [id])
}

SVG generated by prisma-erd-generator:

What I expecting to see in the SVG was: the PK for the orders table should be order_id, PK for the employees table should be employee_id, and PK for customers should be customer_id.

Am I doing something wrong?

[francismanansala]

@francismanansala can you give v1.0.2 a test. I’m trying on my project now but I didn’t have this issue before. Test case was written so I’m assuming this is safe to be closed

Works perfectly within my test scenario and project 🚀 Thanks for the quick turn around on this @keonik!

[keonik]

@francismanansala can you give v1.0.2 a test. I’m trying on my project now but I didn’t have this issue before. Test case was written so I’m assuming this is safe to be closed