Is useField or useForm reactive?

[XEngine]

If I change a property of useField like "standalone" from true to false, will it get update?

const standalone = ref(true)
const {errorMessage, value, handleChange} = useField(name, rules, {standalone: standalone});

standalone.value = false

[logaretm]

some of the useField and useForm options can be reactive refs, but not everything. In the case of standalone, it cannot be reactive because it affects how provide/inject works internally. This is a Vue limitation because you can't call them after the initial setup.

Generally, plenty of useField and useForm options can be reactive, If you are using TypeScript you should be getting type checks already for these. If not, you should read the option type hints in the intellisense menu.

[XEngine]

Hmm, is there any way I can disable the validation in the runtime? I mean in my case, there are some inputs in a form needs to get disabled (but editable) from validating when using handleSubmit.

All I can find this standalone property but I can't switch it after useField initiated, If I used <Field> and make it 'standalone' prop to false would it be effective?

[logaretm]

Why would you need a field to participate in form validation initially then take it out? You can make use of reactive validation schemas to do that where you remove that field validation rules when your condition is met (with computed or ref).

[XEngine]

there are few switches for some cases like "either use saved things, or input manually". They are separeted in child components controlled by a parent so In vee-validate 3 I could simple disable the validation-observer when some conditions met or re-enable it.

I am not using schemas, that is not the way for me and not my habit since I've been using vee-validate 3 since the arrival. But I guess I should :)

[logaretm]

I see, thanks for the clarification. The reason why disabled was removed is that it introduced confusion when it comes to asking if a form is valid or not.

Some users expected disabled to hide the field completely of its parent form which is what standalone does here.

While some only expected it to affect errors messages but leaves out flags and values intact.

So since it is hard to define what is exactly "disabled" this has been removed in favor of users adopting it themselves via computed rules which partially overlaps with this use-case.

There is a way to make standalone reactive but that would effectively make it like disabled and would introduce the same questions again.