-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Description
Note: this issue only refers to v-model for components, and is not considering v-model on DOM elements. There was a discussion which included this unexpected behavior in #6216 , and also a PR #6327 that tried to fixed that, but those also included being able to pass-through v-model to DOM elements, which is not the case with this issue.
Version
2.5.22
Reproduction link
https://codesandbox.io/s/933003yx6w
Steps to reproduce
Use v-model on a component that doesn't have value defined in its props.
What is expected?
value is added to component's instance $attrs
What is actually happening?
value is not added to component's instance $attrs
Because of that, when wrapping a component and passing through the props and event handlers using v-bind="$attrs" v-on="$listeners", v-model will not be (completely) passed through, and will require explicitly defining value in wrapping component's props and passing it using :value="value" to the wrapped component (see the linked sandbox).