Computed properties accumulate from previously inspected components
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with Vue 3.4.11, devtools v7.6.1, Chrome 130 on Windows 10, switching between components with and without computed properties. Start by examining the Vue hooks mentioned in the report; done means computed properties do not persist or attach to unrelated components, and the duplicate computed-property warning no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100