future/useForm: Type regression in v1.13.0 with defaultValue

[transparent-citizen]

Imagine a schema with a required and an optional property.

const schema = coerceFormValue(
	z.object({
		name: z.string(),
		age: z.int().optional(),
	}),
);

✅ Partial default values work fine:

const { fields, form } = useForm({
	defaultValue: {},
	schema,
});

✅ null default values work fine:

const { fields, form } = useForm({
	defaultValue: {
		age: null,
		name: null
	},
	schema,
});

✅ If a field is optional, undefined default values work fine:

const { fields, form } = useForm({
	defaultValue: {
		age: undefined,
	},
	schema,
});

❌ If a field is required, undefined default values throw a type error:

const { fields, form } = useForm({
	defaultValue: {
		name: undefined,
	},
	schema,
});

Type '{ age: null; name: undefined; }' is not assignable to type '{ name?: string | null; age?: string | number | null | undefined; }' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Types of property 'name' are incompatible.
    Type 'undefined' is not assignable to type 'string | null'

Note that exactOptionalPropertyTypes is set to true in tsconfig.json.

This used to work in v1.12.1, so it might be an oversight from the defaultValue revamp from v1.13.0?

[edmundhung]

@transparent-citizen Looks like I tested it without exactOptionalPropertyTypes enabled. Working on a fix now. Thank you!

[edmundhung]

It should be fixed in https://github.com/edmundhung/conform/releases/tag/v1.13.1

[transparent-citizen]

Works flawlessly. Thank you very much!