It would be great for an extension to provide the same filter/search box support that the new Outline view supports. Searching and filter custom views is a request I'm hearing more and more with GitLens.
/cc @jrieken
This would be great, but it doesn't necessarily need to just be filter/search. There are other inputs which would be usefully located in the tree view - renaming, for example, so it would be cool if the API can be fairly generic...
This would be helpful for us on the salesforce test explorer as well. https://github.com/forcedotcom/salesforcedx-vscode/issues/605
I agree the functionality should be generic. Allow extensions to add custom UI to the view's toolbar.
We have another need for this in the Salesforce Extensions: https://github.com/forcedotcom/salesforcedx-vscode/issues/862
does the custom treeProvider will provide a filter/search box? I think this requirement is very necessary, otherwise it is difficult to find the data you want in the case of a lot of data.
Is it possible to open the outline search box and filter it through the label property of the tree node?
@sandy081
Might not be as an API but we are looking to implement a generic filtering for all trees which will just filter the data that is visible.
Might not be as an API but we are looking to implement a generic filtering for all trees which will just filter the data that is visible.
thanks, looking forward to the implementation of the function, where can I get notice if the implementation is complete?
Is there any way to filter the explorer view today?

I don't think so.
I'm looking forward to it as well.
This'd be very useful 馃檱
any update on this?
I'm looking forward to see it as well
Coming from here https://github.com/hbenl/vscode-test-explorer/issues/4
Would be really usefull and make the VSCode experience a step closed to the full VS :)
Now that #63566 has landed, hopefully this can be supported!
With new Tree, custom views can be filtered just like file explorer.
It doesn't search in nested folders which makes this mildly useless and inconsistent ... and it's not an API ... and not a real input. Not hating, just stating.
It is consistent with other trees (file explorer). Exposing as an API is a big ASK which I am afraid might not happen soon.
Closing this as the custom views with new tree supports filtering
@sandy081 Is this feature somewhere documented? Couldn't find it..
@alexr00 Is it documented in 1.37 release notes?
It's called out here which links to more info and includes documentation about the Improved Keyboard Navigation.
Most helpful comment
Might not be as an API but we are looking to implement a generic filtering for all trees which will just filter the data that is visible.