Chris Sobeck

@pedroabreu I agree but it looks like that would produce a new issue due to a race condition, in my case it seems to be referencing prevState when using onChange...

@jaredpalmer and @pedroabreu the better workaround would be using custom onChange handler with setFieldValue('borrower_additional', e.target.value, true) which would trigger validation correctly but it looks like using true there does not...

@pedroabreu avoid the race condi w/ ``` onChange={async e => { await handleChange(e) validateField('borrower_additional') }} ```

If you are having an issue like the latter then you should probably disable validation, events w/false and do field level validation. Ive advised that the recent workaround works just...

I believe there is no solution for this. Only workarounds. I would run the latest version and disable validation so that fields only validate on submit. But I agree. Validations...

What is the specific behavior you are looking for?

@clu7ch3r Except I think you want to return undefined instead of an empty string because I beleive your field will be in error state with a blank message.

@terenceodonoghue Instead of getting so upset you might want to step back for a minute and re-consider your implementation. I may be able to help with that. How long have...

@vsubbotskyy I also chose not to rely on Yup because it has pros/cons depending on the Formik implementation. The lag is a side-effect of your synchronicity. Since Formik relies on...

@terenceodonoghue Ahh. Your challenge is dealing with race conditions from back end validation onBlur? That adds another level of difficulty, understood. I think whatever works to get you unblocked but...