Add a .new() function besides .parse() on Schema

[bjesuiter]

I would like to have a .new() function on a Schema to be able to create an object according to the Schema by hand.

Example

I have the following zod Schemas:

export const MissingDataTransferObject = z.object({
  type: z.literal('missing_data_transfer_object'),
  message: z
    .string()
    .default('The dataTransfer object in the drop event is not available.'),
});
export type MissingDataTransferObject = z.infer<typeof MissingDataTransferObject>;

export const MissingItemsList = z.object({
  type: z.literal('missing_items_list'),
  message: z
    .string()
    .default(
      `The dataTransfer object does not contain the 'items' property defined in the DataTransferItemList Interface. Please use a major and up-to-date browser.`,
    ),
});
export type MissingItemsList = z.infer<typeof MissingItemsList>;

export const DropzoneError = z.discriminatedUnion('type', [
  MissingDataTransferObject,
  MissingItemsList,
]);
export type DropzoneError = z.infer<typeof MayaDropzoneError>;

I'd like to create these Objects like this:

// CAUTION: Imaginary API! 

DropzoneError.new({
  // type should autocomplete in my editor to the allowed literals
  type: ''missing_items_list"
  // optional: pass a message, but you're not forced to, since it's optional in the schema.input<>()
  message: "The .items property is missing!"
})

Why not use .parse()?

When using .parse() with a new object, I don't get autocomplete for the 'type' param => have to double check the plain string i pass there, or I have to wait for the runtime error to happen and catch it that way.

Also, when using z.infer, message is not optional anymore (which is correct).
But then I would have to export z.input additionally to z.infer which clutters my files.

Why add a .new() function?

• it would be fairly trivial (at least from my silly outside perspective)
• then the Zod Schema would feel more like a Data Class, with parsing, creating a new instance and all the zod goodies :)

[bjesuiter]

Update

I'm now solving this with

  DropzoneError.parse({
          type: 'missing_items_list',
 } satisfies NewDropzoneError),
 
 // with NewDropzoneError being 
 export type NewDropzoneError = z.input<typeof DropzoneError>;

It's a little boilerplatey but works ^^

Still, having a .new() function for this would be very nice :)