issue: useForm and useFormContext without FieldValues gives formState.errors object with any instead of FieldError

[Svish]

Version Number

7.32.1

Codesandbox/Expo snack

https://codesandbox.io/s/error-type-issue-with-react-hook-form-ku968b

Steps to reproduce

1. Use Typescript
2. Write a generic component to list all errors in a form
3. Use useFormContext, but do not pass a type for the values, since this component is generic and we don't know which fields are there.
4. Try to loop over the values in the errors object from formState

Notice that you're getting warnings about unsafe any because the error type for some reason ends up as any instead of as FieldError.

Expected behaviour

Expected the type to be the same as it normally is, except for keys to be unknown:

const errors: {
    [x: string]: FieldError | undefined;
}

But instead it ends up as the following, which gives warnings from Typescript and no type-help or type-safety from editor:

const errors: {
    [x: string]: any;
}

If I pass a type for the values, then it becomes for example:

const errors: {
    firstName?: FieldError | undefined;
}

I expected the same object shape without a type for the values

What browsers are you seeing the problem on?

Edge

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[bluebill1049]

It's a current limitation with V7, fixed in the next major version: https://codesandbox.io/s/error-type-issue-with-react-hook-form-forked-otu0nb?file=/src/App.tsx however currently it's blocked by TS 4.7 update at the V8 branch.

[Svish]

Ah, sweet, thanks for quick reply! Then I'll just add a workaround hack for now, and watch for the V8 release 😊👍