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

Provide a way to list dependant extensions #119242

Closed
fbricon opened this issue Mar 18, 2021 · 2 comments
Closed

Provide a way to list dependant extensions #119242

fbricon opened this issue Mar 18, 2021 · 2 comments
Assignees
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@fbricon
Copy link
Contributor

fbricon commented Mar 18, 2021

The vscode-java extension has quite an ecosystem of other extensions on its own. When trying to uninstall it, it'll fail because 'Java Test Runner' extension depends on it for instance. But Also the Java debugger, Project Manager for Java, Tools for Microprofile, Quarkus Tools...
At the moment, there's no way to know which extensions should be uninstalled first. I suggest the Extension view adds a new tab that lists all those dependant extensions, to make it easier to identify what to uninstall (or simply understand the extent one extension's reach).

@rpwnage
Copy link
Contributor

rpwnage commented Mar 18, 2021

I‘d like to take care of this enhancement request together with #119243

@fbricon fbricon changed the title Provide a way to list dependent extensions Provide a way to list dependant extensions Mar 18, 2021
@sandy081 sandy081 added extensions Issues concerning extensions feature-request Request for new features or functionality labels Mar 19, 2021
@sandy081 sandy081 added this to the Backlog milestone Mar 19, 2021
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Dec 6, 2022
@VSCodeTriageBot
Copy link
Collaborator

We closed this issue because we don't plan to address it in the foreseeable future. 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!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

5 participants