Why do I have to specify a name again when using useField's onChange function?

Bug report

Current Behavior

When using the useField() hook, like so:

const [field, meta, helpers] = useField<any>(name);

Then when I want to call field.onChange(), I have to do it like this:

field.onChange(name)(value)

While this doesn't work:

field.onChange(value)

As you can see I have to specify the name once again when calling the onChange(). This seems redundant since

a ) The useField hook is already provided the name
b ) The hook only exposes you to a single field

Expected behavior

I'd expect to be able to call field.onChange without needing to provide the name of the field again.

Suggested solution(s)

Store the field name in the useField hook (I'm guessing that this is already there), then infer the field name in the onChange function (and any other functions that require you to pass a name).

Start at the useField() hook and trace how field.onChange is created and invoked. Confirm the current name-and-value behavior, then check the existing useField coverage if available; done means a field obtained from useField can pass its value directly to onChange without repeating the field name.