v7: `{valueAsNumber: true}` inconsistent

Describe the bug

Hi again! (Sorry for all the issues this week!)

There seem to be multiple things going on:

1. useController({rules: {valueAsNumber: true}}) doesn’t work. (It works with form.register though.)
2. useForm({defaultValues: {field: 0}} doesn’t get used on valueAsNumber fields.
3. With useController() valueAsNumber fields, you have to force a value, or you get a react controlled/uncontrolled warning.

Codesandbox link (Required)

https://codesandbox.io/s/valueasnumber-bugs-ok2oz?file=/src/index.js

To see issues

• 3, change the value of the second slider. You’ll get the error.
• To see issue 2, just look at the default values on all of the sliders, compared to the defaultValues.
• To see issue 1, change the values of all three sliders, then press Submit and look at the console.

Expected behavior

• defaultValues get used on valueAsNumber fields
• useController({rules: {valueAsNumber: true}}) handles values exactly as form.register does.

[bluebill1049]

Thanks for your feedback. I will put that into consideration.

[mikestopcontinues]

Ah, thanks. A few thoughts:

1. My mistake with the defaultValues. Yikes!
2. I think it makes more sense to keep register and useController as aligned as possible, for developer experience. Why have users reimplement getControllerValue logic for no reason?
3. The performance of value-related rules is better than wrapping onChange/onBlur.
4. The docs for useController indicate the rules param is the same as for register. Additionally, the type on useController rules doesn’t actually block any of the value-related props. Screenshot below of TS with no errors…

Use case:

My primary issue here is that I’m using a custom Field component (that gives a label, hover tip, shows errors, changes classNames, etc). Some inputs wrapped by Field are third-party (Slate, color picker, etc), but some are vanilla inputs. It makes the most sense for me to use useController for all of them. It limits the props I have to support, and I can avoid doing anything wonky to pass the form.register().ref through. (No renames or anything.)

I’m actually surprised the code for useController and register diverges so much. I expected useController to only add the extra outputs (fieldState, formState) for convenience.

Anyway, I’m interested to hear what you think.