web component object as props weird usage doesnt update as it should

[q479902964]

Related to #5313

How to solve this problem in vue2 framework?

I have another question. It's strange, I can solve this problem by making a shallow copy when passing the object parameter, but I don't know the reason and i don't think this is a reasonable solution.

[q479902964]

Can anyone help?

[q479902964]

Why can the _resolveProps method in the vueCustomElment class be able to monitor and reset the prop value after vue is externalized, but cannot be monitored without vue being externalized?
This is my idea. I think the reactive change of the array after vue is externalized causes the vue instance to reset the props of the web components, causing the _resolveProps method in the vueCustomElement class to listen and reset the props. Is there a way to listen to props for data hijacking, for example by inheriting the vueCustomElement class.

[q479902964]

Can this problem be solved without externalizing vue?

[LinusBorg]

You are on the wrong track here.

If you have two copies of Vue in a page, the code created with each one will track reactive changes (like mutating an array) independently of the other.

So if a component dependent on copy 1 does a reactive change, that change will not trigger a reactive effect in the second (web) component, which depends on cop, 2, because copy 2 did not track the reactive change, only copy 1 did.

So no, this is not solvable without externalizing Vue

[q479902964]

So I was wondering if I could inherit the vueCustomElement class to hack and track reactive changes in data.

[LinusBorg]

No, don't think that's realistic

[kikoshoung]

Same problem +1