final-form / final-form/react-final-form

Maintaining complete form state after unmount

Open
#992 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
7.4k
Forks
497
PR merge metrics
No merged PRs in 30d

Description

### 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?
"final-form": "^4.20.7",
"react": "^18.1.0",
"react-dom": "^18.1.0",
"react-final-form": "^6.5.9",

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.