John Rom

https://github.com/formium/formik/issues/721

I posted a possible fix here -- if that problem is that autofill is occuring before React initializes. If the problem occurs on future "fill" commands using the autofill after...

I'm a contributor to and not a maintainer of this project. I probably won't be contributing much without commitments to move #3231 forward, as I've already spent enough energy trying...

@gone-skiing agreed. "it's how react works" is not the final answer, but because the current Formik implementation relies on React hooks to manage state internally, a render is required to...

@gone-skiing @tj-mc the solution presented will not make it into the Formik API itself for a variety of reasons. Using an effect, validation does not begin until the render is...

> The solution that works for everyone requires a rewrite of the way Formik accesses state internally, which is a complex issue that we'll be targeting for v3. You can...

This project is very unlikely to get any future releases, so probably best to look elsewhere.

You can track errors anywhere inside of an object or array tree. For example, if I had a field called name in the shape of an object with name.first and...

@timmaloshtan you can declare your own fixes anywhere, but these patches are often placed outside of `src`, like: ``` /your-project /src /your-form.tsx /types /fixes.d.ts ``` Then, you would modify your...

@israelKusayev if you want to act as if the field value changed normally, you can call `formik.handleChange(field.name)(value)`, and all the setFieldTouched, validations, and other events will be called.