initialValues not populating
See original GitHub issueAre you submitting a bug report or a feature request?
Possible BUG
What is the current behavior?
After Updating final-form(4.3.1 ==> 4.8.1 )& react-final-form(3.1.4 ==> 3.6.0) The intialValues do not get populated.
What is the expected behavior?
At first mount the intial values should be populated
Sandbox Link
https://codesandbox.io/s/n993rvz3v4
What’s your environment?
“final-form”: “^4.8.1” “react-final-form”: “^3.6.0”
Other information
- From what i can see the issue first appeared at
react-final-form@3.5.2testing withreact-final-form@3.5.1it works as expected.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Initial values in Formik aren't showing - Stack Overflow
I have created a separate component in which it will render a card with form inside it. I used Formik API to handle...
Read more >Formik does not re-render when initialValues change #811
Generally enableReinitialize only works when initialValues is updated to something that is not deep-equal to the previous initialValues .
Read more >initialValues Question in KendoReact | Telerik Forums
I have a form and I am attempting to populate the initialValues with data returned from an API request. const [customer, setCustomer] =...
Read more >[Solved]-Not able to set initial values of formik form?-Reactjs
Coding example for the question Not able to set initial values of formik form?-Reactjs. ... Initial values are not populating in React Form...
Read more >Validating Initial Values - VeeValidate
You could be tempted to use :value binding to populate your fields' initial values, but that would cause the inputs to be "locked",...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

After playing around with all the dependencies, I have determined that this is a bug with
react-dom@16.2.0, which is fixed inreact-dom@16.3.0andreact-dom@16.4.0. Hard to tell which fix it was, but…This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.