Unexpected behavior on v-model when parent component does not sets v-model to the child component
Version
3.2.25
Reproduction link
Steps to reproduce
See the linked code sandbox.
What is expected?
the child component should not work if the parent does not sets the v-model on child component
What is actually happening?
the child component inherits the 'v-model' what the root component sets on the parent component