Skip to content
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

Allow multiple instances of the File Explorer #76902

Closed
eine opened this issue Jul 8, 2019 · 2 comments
Closed

Allow multiple instances of the File Explorer #76902

eine opened this issue Jul 8, 2019 · 2 comments
Assignees
Labels
feature-request Request for new features or functionality file-explorer Explorer widget issues *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@eine
Copy link

eine commented Jul 8, 2019

Ref #74229
Ref #76302
Ref #76891


[@nicolo-ribaudo#74229]
The file explorer should also allow duplicating the same file tree, like split editor view allows viewing different positions of the same file.


[@1138-4EB#76891]
an alternative I have considered is to use an additional 'subtree view', where the desired file explorer subtree is shown. However, I'm afraid that it is not possible to 'reuse' all the default and custom options that are configured/defined for the File Explorer viewId. I.e., to make a (custom) copy/instance of File Explorer with a limited scope. Hence, I would need to reimplement all the features in the custom view, which sounds as a no-go.

Another approach would be to filter the content of the default File Explorer, instead of trying to reveal some subdir. Is it possible to programmatically filter the content of the File Explorer?

[@isidorn#76891]
We are not exposing the Explorer via the API.

And sorry it is not possible to programmaticly filter the content in the file explorer. It is simply not exposed and this goes with our API rules.

@isidorn isidorn added feature-request Request for new features or functionality file-explorer Explorer widget issues labels Jul 9, 2019
@isidorn isidorn added this to the Backlog milestone Jul 9, 2019
@isidorn
Copy link
Contributor

isidorn commented Jul 9, 2019

Feature request. We do not plan it for the immedaite future, thus assigning to backlog.

@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Oct 9, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 9, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality file-explorer Explorer widget issues *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

2 participants