John Rom

> When a button picks up the [disabled] attribute, focus shifts from the button to the document. Interesting. I never knew about this. The problem seems in fact much worse...

`handleChange('fieldName')` returns a callback that accepts a string value. I would memoize this like : ```jsx const onChange = React.useMemo(() => formik.handleChange(props.name),[props.name]); return ; ```

My personal thoughts on this are here: #3109 We can split it up into using an plugin-based approach for all validator types, like `formik-validator-yup`, `formik-validator-zod`. This would actually require an...

This isn't how I'd recommending connecting to Formik. Formik's context should always be used under a FormikProvider. I'd recommend you decide whether to connect to Formik or not using multiple...

@olignyf the user could technically change the form during submit (unless you prevent this) if you use an async request, cause it to be valid or invalid even though the...

I'm not sure what the purpose of this change is. Are you creating a new status based on the last status? It's not really clear by default where this status...

The simple answer is because dependent fields exist and Formik doesn't currently have a way to declare them out of the box. Therefore if you had a validation like :...

@nickmccurdy this library hasn't had activity in a long time so probably best to look elsewhere. otherwise, it's true that Formik doesn't install Yup, but it is tightly bound to...

> That said, shells using unix paths aren't supported. Git bash uses unix paths like `/c/path/to/whatever` which Windows can't understand. Operating in git bash is akin to running NVM4W on...

Assuming everyone is having the problem on _page load_ and not afterwards, (autofill is populated on page load, instead of clicking the "Fill" button), page-load autofill generally occurs before React...