Yup errors are swallowed

[marcospassos]

Describe the bug When a field has multiple errors, just the one higher in the hierarchy is reported, despite setting criteriaMode: 'all' and earlyAbort: false.

To Reproduce Steps to reproduce the behavior:

1. Open the sandbox
2. Click on Submit
3. Open the console
4. Notice there is a single error for the items field: "items field must have at least 2 items"
5. Now, uncomment line 45
6. Reload the page
7. See it now reports errors on items that should have been reported along with the minimum number of items requirement

Codesandbox link (Required) https://codesandbox.io/s/modest-butterfly-7noyn0?file=/src/App.tsx

Expected behavior All errors.

[bluebill1049]

hook form reconcile errors based on the field name, if you want a group level, you can consider to use trigger('group')

[marcospassos]

I've tried that. It doesn't work either: https://codesandbox.io/s/modest-butterfly-7noyn0?file=/src/App.tsx

[bluebill1049]

then follow the doc try to debug why it's not trigger the error

resolver: async (data, context, options) => {
  // you can debug your validation schema here
  console.log('formData', data)
  console.log('validation result', await anyResolver(schema)(data, context, options))
  return anyResolver(schema)(data, context, options)
},

[marcospassos]

I can confirm it's an issue related to the Yup resolver:

Yup correctly reports the errors: https://codesandbox.io/s/yup-forked-0xsspo?file=/src/index.js

[marcospassos]

I've updated the code sandbox to make the issue more explicit:

[bluebill1049]

It doesn't look like the errors object has associated with the field name, going back to the original comment hook form will require errors to be associated with fields.

https://github.com/react-hook-form/resolvers/blob/master/yup/src/yup.ts#L14-L39

[marcospassos]

Even associating a field name it doesn't work:

[bluebill1049]

I meant the schema, does the schema errors return the field associate path to that field array? Please refer to the source code which i posted above.

[marcospassos]

Yes:

Is it because Yup uses square bracket notation? I don't think so, since the errors are correctly reported when no errors above exist.

[marcospassos]

Here's what this function returns:

All errors are there.

[marcospassos]

Ok, I found the problem. The set method is overriding the item[0] error since it's reported before the item.

This is the value of fieldErrors at each iteration:

Could you please reopen the issue?