How to prevent asssumed null in args for custom resolve based on t.crud pattern

[MJGTwo]

Hello all. Let's assume I have a User model:

model User {
  id                        String             @id @default(cuid())
  email_P                   String             @unique
  email_P_Verified          Boolean?
  first_Name                String?
  last_Name                 String?
  password                  String
}

Now I want the user to be able to update their first name and last name, but not anything else without first providing the password. I still want to keep with the naming convention of t.crud so I have

export const Mutation = schema.mutationType({
  definition(t) {
  //other logic
   t.crud.updateOneUser({
      resolve: async (_parent, {where, data}, { db }) => {
        const {
          password,
          email_P,
          email_P_Verified,
          ...otherData
        } = data;

        return await db.user.update({
          where,
          data: otherData ,
        });
      },
    });

But while running nexus dev I get an error on where inside of await db.user.update(...) saying that the where argument's properties expect either their defined values or undefined, but could potentially receive value | undefined | null.

Is there a way for me to prevent this null from potentially happening while using the t.crud feature? Currently my only way around this is to do stuff like

const where = { id : args.where.id ?? undefined, email_P : args.where.email_P ?? undefined }

But that seems to defeat the purpose of using t.crud with how verbose that can become.

The following versions of nexus and plugins are listed here:

{
    "nexus": "^0.26.1",
    "nexus-plugin-jwt-auth": "^1.3.0",
    "nexus-plugin-prisma": "^0.17.0",
    "nexus-plugin-shield": "^0.2.0",
}