[Forms] Reusable Form Components & Validation Mode pre-submit and post-submit

[JJosephttg]

I have 2 feature requests I would like to make:

1. Often times, we want to reuse form components in other places, but have different forms they are attached to. It gets complicated when you have a form that has a nested property set to represent the part of the form you have abstracted, and then another with a different property structure. It would be nice if form.key() was extensible/you could have form context where you could specify sub-parts of a form to where you could provide a base pathing to the nested property so that the underlying abstracted component could just reference the property name that other forms might share. For example, form A might be { user: { email, password }, ...otherProps } whereas form B is simply { email, password }. Being able to separate the form from the UI component that needs to link to the form would be nice. No other form libraries have this type of functionality

2. A popular validation method for forms is where you do not validate or blur until they submit, and then after submission, it is on change. It would be nice to be able to control what pre and post submit validation does

[rtivital]

1. Abstraction in these cases never works well – there will always be issues with it. Based on my experience, I can advise creating simple forms that do one job instead of complex shared fields abstraction that try to contain the logic for all cases.
2. You can do that by storing submit attempt in state and then changing validateOnBlur option based on the state value.