Closed ValiDrv closed 2 years ago
Hey @ValiDrv
Can you share a minimal reproduction? You can use vite.new/vue
@ValiDrv does this look like it might be the same as #85?
Looks like it, but I didn't try that area l array push pop, I had it with a computed property that returned an array, or an object.
I'll make some test cases for you tomorrow. ( Just to make sure it's not related to vite )
Here is a test project:
https://stackblitz.com/edit/vitejs-vite-wfqrqh?file=src/App.vue
What I found, is that if you close the InfoWindow
via it's X button AND you have MarkerCluster
/CustomMarkers
/Marker
on the map, you get that error.
If you use vue to show/hide it using v-if
, then it doesn't give the error.
The same error happens "randomly" (didn't pinpoint the cause) when we redraw CustomMarkers
(zoom in/out or pan the window)
Tentatively labeling this as a bug until I can take a closer look
The same error happens "randomly" (didn't pinpoint the cause) when we redraw
CustomMarkers
(zoom in/out or pan the window)
This sounds a lot like what I'm seeing in #85. I suspect these two issues may have the same root cause.
This should be fixed in v0.13.1
. Let me know if the issue persists or if you encounter other issues.
In preliminary tests it looks like it's working, thank you.
There seems to be an issue with removing components that use
<slot />
This will work:
This will give errors:
Errors:
Seems to be the case for
CustomMarker
also (gives the error when computedThis works:
<Marker v-for="m of markers" :options="m.options" :key="m.id">...</Marker>
This gives errors:<CustomMarker v-for="m of markers" :options="m.options" :key="m.id">...</CustomMarker>