Yup schema.validate() options, show every error of a field at the same time

Nobody has claimed this yet.

Hi, sorry I didn't find another issue related to this problem. And since yup has first class support I thought it would be justified to ask about it.

So I'm trying to set an option, mainly here the abortEarly option. My goal is to have a password field with multiple errors displayed and it seems it was the only way. Couldn't find how to do that with validateSchema()

So I did the following instead:

```
validate: (values) => {
const schema = Yup.object().shape({
email: Yup.string()
.matches(/georges.abitbol@gmail.com/, 'cant change email'),
providerName: Yup.string()
.required('type your name'),
password: Yup.string()
.min(8, 'at least 8 chars')
.matches(/[a-z]/, 'at least one lowercase char')
.matches(/[A-Z]/, 'at least one uppercase char')
.matches(/[a-zA-Z]+[^a-zA-Z\s]+/, 'at least 1 number or special char (@,!,#, etc).'),
passwordConfirm: Yup.string()
.equalTo(Yup.ref('password'), 'passwords don't match')
})

return schema.validate(values, { abortEarly: false })
.then(() => {})
.catch((err) => {
throw err
})
}
```

This way I can get every error of a single field and map them to my components to display every error of a field at the same time. Isn't there a cleaner way ? Also I think it could be a good use case to showcase ? Thanks

Start by tracing Formik's validateSchema() path and compare it with the Yup schema.validate() call shown in the issue, focusing on how abortEarly and multiple errors are handled. Done means determining whether the validation path can expose every error for one field and documenting or implementing the supported behavior, with relevant tests added if the project has coverage for this path.

Written by the indexing model from the issue text.