You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you submitting a bug report or a feature request?
Feature request
What is the current behavior?
I'm migrating our front-end infrastructure from redux-form, where we have projects with multiple forms with destroyOnUnmount={false} set on the (redux-form) Form.
In my apps we have wizard type processes, and other CRUD type apps where a record is displayed across multiple tabs with a form used on each tab. To easily visualise a page/tab's validation state I find it convenient to have distinct forms for each.
In redux-form, the complete form state persists in the redux store when destroyOnUnmount={false} is set, which means when remounting the form component the complete state is rehydrated (visited, touched, error, etc).
Wondering what is the approach to achieve this using react-final-form?
Are you submitting a bug report or a feature request?
Feature request
What is the current behavior?
I'm migrating our front-end infrastructure from redux-form, where we have projects with multiple forms with destroyOnUnmount={false} set on the (redux-form) Form.
In my apps we have wizard type processes, and other CRUD type apps where a record is displayed across multiple tabs with a form used on each tab. To easily visualise a page/tab's validation state I find it convenient to have distinct forms for each.
In redux-form, the complete form state persists in the redux store when destroyOnUnmount={false} is set, which means when remounting the form component the complete state is rehydrated (visited, touched, error, etc).
Wondering what is the approach to achieve this using react-final-form?
What's your environment?
The text was updated successfully, but these errors were encountered: