vuejs / vuejs/devtools

Hiding components from the devtools

Open
#794 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.9k
Forks
279
PR merge metrics
No merged PRs in 30d

Description

When working with component libraries the component tree can become cluttered an hard to read, having a way to hide a selection of components without hiding their children would be nice.

This could be a simple includes/exclude filter somewhere (either in the devtools themselves or in the config) but I think a layer system would be more useful especially if one uses components from various sources or just has a lot of components. How those layers would be defined would depend on the requirements I suppose but a good start could be the name of the package it comes from, a more involved implementation could provide a composable that allows the component to define which layer it wants to be affected to (something like useDevToolsLayer('my-layer')).

Another approach could be to use symbols like - in the "Find components..." field to do a reverse search but that would not be intuitive and would also requires to set this value manually every time you refresh the page.

related issue in vuejs/devtools-v6 Hide components from the vue-devtools #1290

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the related vuejs/devtools-v6 issue and locating the devtools component-tree and “Find components...” entry points. Clarify whether the goal is filtering, persistent reverse search, or a layer system, including how child components should remain visible. Done means a defined hiding behavior and an agreed implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.