Binding the components with Vue (two-way v-model) #64
Replies: 2 comments 3 replies
-
Testing this further, this seems to be some initialization issue. Further changes to the reactive value seem to propagate fine. |
Beta Was this translation helpful? Give feedback.
-
It's been awhile since I've used Vue, but I'm seeing this in the playground:
I'm not sure what exactly Vue does to treat custom elements differently, but my guess is it's binding the value as a property before isCustomElement: (tag) => tag.startsWith('wa-'), I couldn't figure out where to add this in the playground. It looks like it's a Vite config now. 😕 If it is an initialization issue and the above doesn't solve it, please post back. We may need to add some guidance on how to register WA elements before Vue initializes or something. /cc @KonnorRogers |
Beta Was this translation helpful? Give feedback.
-
I'm running into a strange problem, where I can wrap the components into a Vue component, having it expose the current value, but the other direction doesn't seem to be working.
Notably, binding
value
to a reactive variable doesn't seem to work.Playground
Beta Was this translation helpful? Give feedback.
All reactions