-
Notifications
You must be signed in to change notification settings - Fork 93
Description
Hello,
i love your lib and i use it widely, but there was one thing i missed so i implemented some sort of "cloning", but that was very very poor and after updating vue to the latest version it broke partly
what i want to do:
create a tippy with a component:
<tippy placement="left" <!-- this is the "default" !-->
:interactive="true"
:arrow="true"
maxWidth="none"
trigger="click"
clone="group1">
<!-- Content -->
<template #content>
<myCompoent :objId="selectedId" />
</template>
</tippy>
as you can see, this tippy has no trigger, its just a "content-tippy"
now, i can do somehting like:
<div @click="selectedId=id" v-tippy="{ clone: 'group1', trigger: 'click' /* trigger gets overwritten, although its the same as in content-tippy */ }">
<div @click="selectedId=id" v-tippy="{ clone: 'group1', trigger: 'click' }">
<div @click="selectedId=id" v-tippy="{ clone: 'group1', trigger: 'click' }">
<div @click="selectedId=id" v-tippy="{ clone: 'group1', trigger: 'click' }">
<div @click="selectedId=id" v-tippy="{ clone: 'group1', trigger: 'click' }">
.... and so on, assume 100+ elements
now for every element, the one and only tippy will be reused, without creating new instances
is something like this already possible or would it be possible to implement?
why?
i often use it for additional information in large lists, sometimes loading also additional data within the component
lets assume a list of 100 entries with 2 tippys per row, one static, one loads additional data
this results in 200 additional vue-components and 100 additional requests to the server
instead i would like to have just 2 additional vue-components and 1 request (plus more requests if the props of the components that loads async data change)