The type of setFieldValue seems incorrect.

[NagaiKoki]

Bug report

The following Eslint error appeared in the setFieldValue function when updating to version 2.3.2 of formik.

Avoid referencing unbound methods which may cause unintentional scoping of `this`.
If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.eslint@typescript-eslint/ unbound-method

When I look at the FormikHelpers types, though, they were defined as follows,

setFieldValue(field: string, value: any, shouldValidate?: boolean): Promise<void | FormikErrors<Values>>;.

However, looking at the implementation, I think the correct type is

setFieldValue: (field: string, value: any, shouldValidate?: boolean) => Promise<void | FormikErrors<Values>>;

Is this type correct?

Current Behavior

export interface FormikHelpers<Values> {
    // ...
    setFieldValue(field: string, value: any, shouldValidate?: boolean): Promise<void | FormikErrors<Values>>;
     // ...
}

Expected behavior

export interface FormikHelpers<Values> {
    // ...
    setFieldValue: (field: string, value: any, shouldValidate?: boolean) => Promise<void | FormikErrors<Values>>;
  // ...
}

Reproducible example

• access formik.setFieldError and eslint @typescript-eslint/unbound-method get enabled

Suggested solution(s)

Additional context

Your environment

Software	Version(s)
Formik	2.4.0
React	18.2.0
TypeScript	5.0.0
Browser
npm/Yarn	yarn
Operating System

[quantizor]

We can fix this, but it's probably also better to not check types that aren't yours with https://www.typescriptlang.org/tsconfig#skipLibCheck

[klarstrup]

I face this issue with skipLibCheck enabled.

[quantizor]

Fixed in https://github.com/jaredpalmer/formik/releases/tag/formik%402.4.1, thanks for contributing!

[NagaiKoki]

@probablyup Thank you!