react-hook-form: ESlint TypeScript error `unbound-method`

Thank YOU. v7 looks great! Can’t wait to use it in production 😊

Going to try to resolve this at v7.

I am going to close this issue, this will be fixed in v7 (release in 2 weeks) 👍

@bluebill1049 even after v7 release the error is present.

I just updated & uploaded repo with repoduction in CI. PR with build here: https://github.com/Tymek/rfh-eslint/pull/1, with version 7-alpha.0

All checks have passed!!! ✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️

(v6 failing: https://github.com/Tymek/rfh-eslint/runs/1765302666)

neither xD

WIP here: https://github.com/Tymek/react-hook-form/pull/22/files

How I understand current situation with this refactor: Problem is, previously type-checking was terminated whenever we where using Control. Control was terminating what could/couldn’t be passed and was defaulting/casting it to Record<string, any> every time. This way many things where compatible, for example: strict useForm<FValues>() with loose useFormContext()

With the changes, strict and specific Control<FormValues> was not compatible with generic TControl or Control<any>

First, I will try to find a way to make something like Control<{ x: string, y: string }> match when we need Control<{ x: string }> in useWatch and other similar cases.

Second, how rigid should it be about passing strict-typed Control into those functions?

  const FValues = {
    x: string,
    y: string,
  }

  const { control } = useForm<FValues>() // strict
  const A = useWatch<FValues>({ name: 'x', control }) // will work
  const B = useWatch({ name: 'x', control }) // "loose"? should probably be allowed

Maybe in this case allowed values for name can be inferred from control? I just hope reverting to weird 💫 FieldValuesFromControl is not necessary.

I could reproduce reported error #3002 with app/src/useWatch.tsx test. Thx @maxsbelt, I will check what’s going on with watch signature.

Now I will continue toying with this issue on a side 😉. Extensive testing will be needed.

@Tymek I created a sandbox with a simple reproducible example: https://codesandbox.io/s/fervent-haibt-t5zmi?file=/src/useMyForm.ts

I got different results with:

export type Control<TFieldValues extends FieldValues = FieldValues> = Pick<
  UseFormMethods<TFieldValues>,
  'register' | 'unregister' // ...
> & {

vs

export type Control<TFieldValues extends FieldValues = FieldValues> = {
  register: UseFormMethods<TFieldValues>['register'];
  unregister: UseFormMethods<TFieldValues>['unregister'];
  // ...

wut. 😦

I think I had some tests or branch with modified ESlint config. I’ll check this in a day or two and let you know how

I guess you can mute the error using @ts-expect-error, and it will also notify you when the problem is resolved (aka there is no error anymore)

thanks @Pirastrino 🙏 pretty sure @Tymek already tried that.