-
## 🐛 Bug report
### Current Behavior
I'm trying to add an 'onChange' event to a without losing existing behavior to update/ store the field value.
By default if I specify an onChange handler, …
-
## 🐛 Bug report
### Current Behavior
When blurring a Field or FastField the entire form re-renders, even if there are no changes.
Custom fields with useField and value/setValue don't exhibit th…
-
## Bug report
### Current Behavior
When using similar field components in a nested form object, the touched object is not created accurately at pre-submit phase.
Pressing submit does not show t…
-
I'm really trying to wrap my head around why this is a design choice and how it's not more of an issue.
I have a form that has a number of inputs on it, and when I start typing in any of the fields…
-
## Bug report
### Current Behavior
`useFormik` hook creates new formik instance each time being called
### Expected behavior
Expected `useFormik` hook to return the same instance of formik…
-
## 🚀 Feature request
I'm trying to use `useField` hook to connect formik to custom component:
My custom component uses objects as a value:
```javascript
const CustomComponent = ({ value, onChang…
-
## Bug report
### Current Behavior
When we select a data we get the error pleas…
-
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
When we use datepicker with formik it fails because formi…
-
## 🐛 Bug report
### Current Behavior
I have an application with multiple forms and I found some memory leaks due to Formik. To be sure Formik is the problem, I created a new app with create-reac…
-
I have some trouble getting my head around a breaking change introduces in Yup with version '0.29.0' in combination with Formik.
Namely it's about the following:
`the types ([@types/yup](https://…