Repository navigation
Maybe<T> not undefined for optional strings using z.string().nullish() with zod #1086
Description
Hello, thanks for this codegen plugin!
However, I seem to have a problem with zod:
Given the GraphQL Schema e.g.:
input AppointmentInput {
description: String
...(Optional String description)
The generated Schema is:
export function AppointmentInputSchema(): z.ZodObject<Properties<AppointmentInput>> {
return z.object({
description: z.string().nullish(),this is giving me an error saying:
Type 'undefined' is not assignable to type 'InputMaybe'
The error goes away if I manually change it to:
...
description: z.string().nullable(),
...( nullable instead of nullish)
My config is:
config: {
importFrom: "./schema",
withObjectType: true,
useTypeImports: true,
schema: "zod",
strictScalars: true,
}
Using:
"graphql-codegen-typescript-validation-schema": "^0.17.1"
"zod": "^3.24.4"
Activity
Code-Hex commentedon Sep 23, 2025
@ChrisEnglert Sorry for the late reply. I just released 0.18.0, so please try it. If you can still reproduce the issue, it would be very helpful if you could provide an environment where you can reproduce it, such as on codesandbox.
supernaut commentedon Oct 8, 2025
I have the same issue in version 0.18.1. Replacing
.nullishwith.nullablefixes the issue.flesler commentedon Oct 22, 2025
IMO there should be a setting that defaults to
.nullish()and can be overriden, just like custom scalars. For those that need.optional()or.nullable()(depending on the case). Right now I'm handling in a post-processing script, which is not idealCode-Hex commentedon Apr 25, 2026
Fixed in #1423. Zod nullable field generation is now configurable, so projects whose Maybe type does not include undefined can opt into nullable instead of nullish.