TreeView search/filter input & api for customization

[MaxKless]

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:

• control over whether a separate input field should be shown above a tree (like the one in the extensions or scm views)
• callbacks including the search contents that can be used to populate the tree with items.

Thanks for considering this and thanks for an overall great developer experience with vscode :)

[alexr00]

control over whether a separate input field should be shown above a tree (like the one in the extensions or scm views)

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.

callbacks including the search contents that can be used to populate the tree with items.

This is a fair feature request.

[vscodenpa]

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!

[MaxKless]

Ok that makes sense. Thanks for the feedback.

[vscodenpa]

🙂 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!