Inappropriate behavor of compatConfig with feature COMPONENT_V_MODEL on pre-component basis
Vue version
3.2.37
Link to minimal reproduction
Steps to reproduce
In @vue/compat environment with compat MODE=2, define two components: App and Child. Wherein, Child meets v-model api of vue3. Now, refer to Child in App and deliver value using v-model. I add compatConfig in App: {COMPONENT_V_MODEL: false} to make App action like it is in vue3 env with v-model.
What is expected?
Child could get right value: modelValue
What is actually happening?
Child receives a attribute: value. To achieve expected target, I have to add the same compatConfig in Child.
System Info
No response
Any additional comments?
Strictly speaking, this is not a bug. However, this behavior seem to be not appropriate for two reasons:
- A developer has to change parent component's behavior by add config in child.ren component
- Generally, we using third-party component more often, so we can not add config in children component. It seem to be more appropriate to add this config in parent component.