Computed properties accumulate from previously inspected components

[MetRonnie]

There seems to be a bug where all the computed properties from all previously inspected components accumulate in the devtools, displaying as undefined, or old values. So you might end up selecting a component with no computed properties, and seeing this:

Seen on v7.6.1 of the extension, Vue v3.4.11, Chrome 130.0.6723.92, Windows 10

Edit: this seems worse than I first thought, it seems the hooks into Vue are actually causing these computed properties to get attached to components that shouldn't have them? I've started getting this warning which goes away when the extension is disabled:

[Vue warn]: Computed property "id" is already defined in Props.

[cutlerrickel]

@MetRonnie Did you figure this out?

[MetRonnie]

@cutlerrickel What do you mean? This is a bug report.

[cutlerrickel]

@MetRonnie My apologies. However, I was able to eliminate this same behavior by removing vuetify. It looks like they may be causing the pollution of the computed properties. I have not been able to figure out why, though.

[MetRonnie]

Interesting. I am using Vuetify 3.7.4. But I have not had this problem before with older versions of Vue devtools

[cutlerrickel]

@MetRonnie did you also upgrade Vue during that time as well? I'll keep looking into it.

[MetRonnie]

I tried upgrading to the latest version of Vue but still encountered the problem

[alexzhang1030]

Related #535