Skip to content

Bug: setValue on nested v-model do not correctly update parent #2468

@tharvik

Description

@tharvik

Describe the bug
with nested v-model components, updating the child doesn't propagate changes to the parents, only the direct one.

To Reproduce
I setup a PR with a test triggering it. the normal vue behavior can be testing in this playground

Expected behavior
in nested v-model, if the child changes, it should update all it's depending parents, as vue does.

Related information:
it look like that setValue replace the ref of a model by the value directly. it should update the ref instead.

Additional context
I was able to workaround it by replacing in my test stack

comp.setValue("value");

by

comp.vm.modelValue.value = "value";

EDIT: workaround is not working for deeper hierarchy

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions