computedTypesResolver does not work with nested fields

Describe the bug

I have a schema like so:

const schema = Schema({
  top: string.min(100),

  nested: Schema({
    value: string.min(100),
  }),
})

Errors in the top-level fields are reported correctly, while errors in nested fields are lost.

To Reproduce

1. Go to https://codesandbox.io/s/react-hook-form-computed-types-nested-fields-validation-error-bug-9uuuuq?file=/src/index.jsx
2. Run
3. See in the console how the error on the ‘top’ field is reported but not on the nested field.

Codesandbox link (Required)

https://codesandbox.io/s/react-hook-form-computed-types-nested-fields-validation-error-bug-9uuuuq?file=/src/index.jsx

Additional context

Not sure what the expected shape of FieldErrors should be, if it should be a nested object or flat where keys are dot-separated field paths. If the later then fixing computedTypesResolver can be as easy as changing parseErrorSchema like so:

const parseErrorSchema = (computedTypesError: ValidationError): FieldErrors => {
  const parsedErrors: FieldErrors = {};

  for (const { path, error } of computedTypesError.errors || []) {
    parsedErrors[path.join(".")] = {
      type: error.name,
      message: error.message,
    };
  }

  return parsedErrors;
};

[bluebill1049]

The way errors get parsed is pretty much like get/set method.

test.test.test

to become

{test: {test: test{}}}

[bluebill1049]

any update on this issue? or is there anything we can need to patch for resolver?