use DeepPartial for acceptable DataType into ValidatedForm

[Alex-Yakubovsky]

closes #313

• Adds a DeepPartial type
• Uses DeepPartial for default types, allowing users to pre-set set a subset of deeply nested fields (useful for arrays and nested types)

// example todo validator
const validator = withZod(
  z.array(
    z.object({
      title: z.string()
      dueDate: z.string()
    })
  )
);

...

<ValidatedForm validator={validator} defaultValues={[{ title: 'my todo' }]}> // Without a `DeepPartial` this causes a type error
   // ...
</ValidatedForm>

• Updates DataType to extend { [fieldName: string]: any } for ValidatedForm
  • My understanding is that is a requirement anyway, but without explicitly specifying the constraint DeepPartial will cause a type error on the InternalFormContextValue. This is because DeepPartial<DataType> will unpack as DataType | { P in keyof DataType]?: DeepPartial<DataType[P]> | undefined. Since DataType could be anything, it isn't assignable to the expected { [fieldName: string]: any; } for defaultValuesProp

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
remix-validated-form	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 12, 2023 5:15pm

[airjp73]

Thanks!