-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation values are stale #102
Comments
This is related to jaredpalmer/formik#2083. Works fine with formik v1.5.8 |
@warrenday is this still an issue with formik v2.0.8? |
@warrenday I'm seeing this behavior as well after upgrading to latest Formik. Can't speak to the specific way you have your form / field set up, but in our case in v1.5.2 (previous version our project was on) the validation fires twice on change, the second time with the fresh value. In v2.0.8, it fires twice on change, the second time using the stale value. It also seems that setting |
this should be fixed in v1.6.3 and v1.7.0-beta.1 |
When using fields such as "TimePicker" or "DatePicker". The values passed into Formiks "validate" or "validateSchema" are incorrect. The callback is showing stale values.
This is only true when validation is called after an
onBlur
event.onChange
works fine.The text was updated successfully, but these errors were encountered: