Using feTS with Prisma client code-generation, undefined vs null

[caprica]

I use Prisma with code-generated schema types, and I am trying to return one of those schema types via a feTS router in NextJS.

Following the documentation, I use createRouter() and add my endpoint.

If all of my Prisma types are mandatory, then everything is fine.

prisma.schema:

model Person {
  userId                  String                 @unique
  role                    String
}

[...slug].ts

const PersonSchema = {
  type: 'object',
  properties: {
    userId: { type: 'string' },
    role: { type: 'string' },
  },
  required: ['userId', 'role'],
}

But if any of my Prisma fields are not mandatory, I get Typescript errors, for example here I'll make "role" optional in the Prisma schema and in the feTS router definition.

prisma.schema:

model Person {
  userId                  String                 @unique
  role                    String?
}

[...slug].ts

const PersonSchema = {
  type: 'object',
  properties: {
    userId: { type: 'string' },
    role: { type: 'string' },
  },
  required: ['userId'],
}

I think this occurs because the code-generated Prisma client API code uses null for these non-mandatory fields, not 'undefined'. I think in Prisma undefined means "do nothing" rather than "no value".

If I hack the type to undefined instead , the Typescript error goes away. Obviously this was just hacking for this issue and is not a proper solution.

Maybe related to #402.

What can I do here to resolve this?