required/defaultValue behavior unintuitive

[jancbeck]

Let's say I set a default value to my collection field like so:

export const Users: CollectionConfig = {
  slug: "users",
  fields: [
    {
      name: "name",
      type: "text",
      required: true,
    },
    {
      name: "subscriptionActive",
      type: "checkbox",
      defaultValue: true,
      required: true,
    },
  }]
}

Because of required: true, whenever I use user.subscriptionActive I don't have to do nullchecks and instead can treat it as always being a boolean.

export default async function Page({ params: paramsPromise }: Args) {
  const { id = "" } = await paramsPromise
  const user = await payload.findByID({
    collection: "users",
    id,
  })

  if (!user.subscriptionActive) {
    throw new Error("User subscription expired")
  }

Great! But now when I create a new user...

const newUser = await payload.create({
    collection: "users",
    data: {
      name: input.name,
    },
  })

Typescript complains:

Type '{ name: string }' is not assignable to type 'Omit<User, "sizes" | "createdAt" | "updatedAt" | "id"> & Partial<Pick<User, "sizes" | "createdAt" | "updatedAt" | "id">>'.
Property 'subscriptionActive' is missing in type '{ name: string; }' but required in type 'Omit<User, "sizes" | "createdAt" | "updatedAt" | "id">'.ts(2322)

But that's why I defined a default value! So that I don't have to explicitly declare it every time...
I'd expect Local API types to know that subscriptionActive is optional once a defaultValue is defined.

Maybe someone can help me understand why this is not the current behavior.