Resolver Generated for Non-Scalar Fields Does Not Reflect name From Prisma Schema for Primary Keys

[jpulec]

Description

One of the features of prisma is that it allows changing the internally generated name for a composite primary key. It looks like nexus-prisma is hard-coded to use the default name, which means that generated resolvers try to perform lookups that don't exist.

Repro Steps/Link

Create the following Prisma models, and schema definitions.

model Order {
  orderNo Int
  orderCustomerId Int

  orderItems OrderItem[]

  @id([orderNo, orderCustomerId], name: "customerOrder")
}

model OrderItem {
  orderNo Int  orderCustomerId Int

  order Order @relation(fields: [orderNo, orderCustomerId], references: [orderNo, orderCustomerId])
}

import { Order } from "nexus-prisma";

const SchemaOrder = objectType({
  name: "SchemaOrder",
  definition(t) {
    t.field(order.orderItems);
  }
});

Trying to query for orderItems above, will generate the following prisma query, first trying to fetch the order, and then using the fluent api:

prisma.order.findUnique({
  where: {
    orderNo_orderCustomerId: {
      orderNo,
      orderCustomerId,
    }
  }
});

This query bombs since the correct name for the lookup has been mapped to customerOrder but nexus-prisma does not reflect that.