how to migrate v-model to setFieldValue ?

[sschneider-ihre-pvs]

in v4.6.6 I used to do the following v-model="values.something" just to provide a starting value for the child component. That will now cause a readonly warning. if I just do :modelValue the value also does not get updated from the input.

[logaretm]

First, that was never encouraged in the docs to begin with and now I've added more docs to that area in the guide section.

So you have a few ways to migrate to:

• Make use of defineComponentBinds.
• You may want to use useFieldModel but the binds API is just a better alternative.
• Or roll your own proxy that uses setFieldValue.

const proxy = computed({
  get: () => values[field],
  set(value) {
    setFieldValue(field, value);
  }
})l

But that's basically the same outcome, you will need to define your fields. Another alternative entirely is to use useField inside your input components and you shouldn't need to predefined your fields in the script anymore.

If none of these are good alternatives for you then I suppose I could expose a writable version of values so you could keep dong the same as what you were doing but won't be mentioned in the docs. Something like __mutableValues.

[hinogi]

https://stackblitz.com/edit/vee-validate-v4-quasar-framework-sbadmh?file=src%2FApp.vue this is what I currently have. q-input has a required prop modelValue so if I only use v-bind typescript/volar will tell me that this component requires a modelValue

[hinogi]

How to I convert the input value to number? v-model.number did that before.