-
### Describe the bug
Bad performance with 100+ rows in an array field
### Your minimal, reproducible example
https://codesandbox.io/p/sandbox/broken-silence-cwwxtp
### Steps to reproduce
1. Click…
-
## Bug report
### Current Behavior
The form is correctly validated on mount but then when the form gets reinitialized because initialValues have changed, validation is not re-triggered.
### E…
-
## 🐛 Bug report
### Current Behavior
When calling submitForm on an invalid form, the returned promise is resolved.
### Expected behavior
When calling submitForm on an invalid form, the…
-
## 🐛 Bug report
### Current Behavior
I have a form with a complex validation logic that runs on the server.
Sometimes I am seeing stale validation errors being shown on the form.
This seems t…
-
## 🐛 Bug report
### Current Behavior
If you throw an empty errors object, validation passes validation successfully
### Expected behavior
While in sync mode returning an empty errors object is…
-
Proposal for improving the documentation:
The "Forms" section of the ReactJS documentation recommends using additional libraries for forms validation/error messages/etc.. It also explicitly names t…
-
## Bug report
When `validateOnMount` is true and the form fails the validation initially, after passing the validation and submit the form, the initial errors are populated again
### Current Behav…
-
## Bug report
### Current Behavior
Validation Error doesn't trigger on radio button fields even when validateOnblur property is set to be true in Formik. It is working fine when validateonChange…
-
I'm trying to reference a field outside the current yup object. In this example, `car` should only be required when `name==='Pete'`.
I found that the `when` function in Yup only has access to the cur…
-
There are some validation scenarios that cannot be dealt with formik and require the proper graphql error message to be displayed on the front end:
- [ ] Email already in use