Props can be provided with a setter.

[infinnie]

Rendered

[ycmjason]

I'm totally loving this idea.

[ycmjason]

On second thought, it will be quite weird if I did props.x = 3 but it doesn't actually set x to 3.

[phiter]

I like the idea because I see myself doing this quite often:

<dialog v-model="isOpen" />

props: {
    open: {
        type: Boolean,
        default: false,
    }
},
computed: {
    isOpen: {
        get() {
            return this.open;
        },
        set(v) {
            this.$emit('update:open', v);
        }
    }
}

Adding a setter to the props would definitely reduce this boilerplate that I have to use for some wrapper components.

[pikax]

if using composition-api you can have a helper to handle that:

function useVModel(props, name, emit){
return computed({ 
  get(){
    return props[name]
  },
  set(v){
    emit('update:'+name, v);
  }
})
}

defineComponent({
      template: `<div>
      <label :for="child-input">Update value</label>
      <input name="child-input" v-model="value">
      </div>`,
      props: {
        value: String
      },
      setup(props, {emit}) {
        const value = useVModel(props, "value", emit);

        return {
          value
        };
      }
    })

With typescript