Deprecate validation in <Form>

[Tobbe]

The <Form> component takes a validation prop, but it's really so much more. It's passed straight in to react-hook-form's useForm and can so take all the available config options, not just validation related.

This should be reflected in the name of the variable. Something like formOptions would fit with the already existing formMethods. The names of the respective TS types are UseFormOptions and UseFormMethods.

The prop is used in the tutorial like this:

// web/src/pages/ContactPage/ContactPage.js

<Form onSubmit={onSubmit} validation={{ mode: 'onBlur' }}>

So it does read very well. Better than formOptions={{ mode: 'onBlur' }} would.

Going forward I see two options

1. Deprecate validation and point people towards formOptions instead
2. Keep validation, but make it only take the mode parameter (possibly also reValidateMode as that also has to do with validation). And then additionally add formOptions for controlling everything.

This is the list of everything you can pass to useForm

const { register } = useForm({
  mode: 'onSubmit',
  reValidateMode: 'onChange',
  defaultValues: {},
  resolver: undefined,
  context: undefined,
  criteriaMode: "firstError",
  shouldFocusError: true,
  shouldUnregister: true,
})

[thedavidprice]

This is a great idea. To keep it backwards compatible, I'd like us to go with your recommend option 2.

Will see if we can link this together with #2270

[jtoar]

Note that the names of the types have changed: https://github.com/react-hook-form/react-hook-form/blob/master/CHANGELOG.md#changes-13

• UseFormOptions -> UseFormProps
• UseFormMethods -> UseFormReturn

[thedavidprice]

@jtoar Will the final implementation of #3376 close this one?