DataTable or Column leak computed properties to their children through VirtualScroller

[Kotoriii]

Describe the bug

Using a DataTable > Column > Custom component structure like

<DataTable>
  <Column>
    <CustomComponent />
  </Column>
</DataTable>

Makes the custom component inherit implicit computed properties coming from the DataTable / Column Primevue components. This creates performance and name clashing issues.

Since CodeSandBox does not support Vue Dev Tools, I can only post screenshots of my local DevTools findings.

PrimeVue Component / (Inside DataTable->Column)

Custom Component (Inside Column)

The leaked properties seem to come from an implicit VirtualScroller inject

It would be great to know why this happens and if it can be prevented in any way. I'm checking the vue 2 version, and this doesn't happen there.

Reproducer

N/A

PrimeVue version

3.15.0

Vue version

3.x

Language

ES6

Build / Runtime

Vue CLI App

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

[github-actions]

We're unable to replicate your issue, if you are able to create a reproducer or add details please edit this issue. This issue will be closed if no activities in 20 days.

[luizzappa]

I am facing this warning using the DataTable component which seems to be related to this issue.

The structure of my code is more or less like this:

        <DataTable 
            :globalFilterFields="['alias', 'licenseKey', 'usage', 'status']" 
            v-model:filters="filters"
            filterDisplay="menu"
        >
          <Column field="alias" header="Alias" sortable bodyStyle="width: 35%">
            <template #filter="{ filterModel }">
              <InputText v-model="filterModel.value" type="text" class="p-column-filter" placeholder="Search by alias" />
            </template>
          </Column>
        </DataTable >

My environment: nuxt + primevue (nuxt-primevue) + windows 10 + chrome.

The error never happens the first time I load the page, but if I navigate to another page and return, it appears
(sometimes I have to browse more than once to appear). It should happen when the component is already mounted on the client side.

[mertsincan]

The original issue has been fixed. For the other issue, please track #4745

Best Regards,