John Rom

Now that I think about it, setFieldTouched is only called on blur and during a submission attempt. Touched in formik implies that if the field isn't valid, the user will...

No, open source moves slowly since people are mostly volunteering their time in the middle of other projects. I agree the error should propagate, but for backwards compatibility purposes we...

Yes, a screenshot is not accessible to all users, so descriptions of issues should be clearly written in text. Additionally, I already put my thoughts above and it is rude...

I agree it's a weird place to choose to catch an error. I have an entire v3 PR #3231 which needs a few final touches but I haven't gotten any...

In v3 the Formik API will have a function called `getState()` which will return the entireity of Formik's internal state and can be used in a callback like this. #3231...

Another thing to consider is we already have a request to add a prop to onSubmit for context, #2437, basically just any old information that needs to be sent, like...

This might be fixed in #3231 just because the underlying state manager `useSubscription` checks for unmounts, I think.

Not to disagree with the need to expose more of the API during submit, I do have a note to the OP: > re-sending unchanged form values generally increases the...

@ops1ops errors should not appear on the form because the error message component provided by Formik checks to see if a field has been touched (`formikProps.touched.myFieldName`). If you're using your...

@ops1ops a field is marked as touched after its first change if you use the API provided by formik. if you use `setFieldValue`, this might not be the case (code...