-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TreeView search/filter input & api for customization #161753
Comments
This we will not do, as the ctrl+f command is our unified tree search mechanism. We will not use a different search UX for extension trees vs. core trees.
This is a fair feature request. |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Ok that makes sense. Thanks for the feedback. |
🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
That's pretty much what I'm trying to achieve with this feature :p |
This would indeed be a lovely feature addition to the tree view API, hoping it gets picked up at some point |
Is there any progress on this issue |
As was talked about in #70646, searching/filtering custom trees is really hard currently. Even if you get the unintuitive feature to work, as an extension author you have no control over how the tree will be updated.
To provide a better UX, it would be really nice to have fine-grained control over tree filtering via the vscode extension api:
Thanks for considering this and thanks for an overall great developer experience with vscode :)
The text was updated successfully, but these errors were encountered: