-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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
When uninstalling an extension, ask to also uninstall extensions that depend on it #119243
Comments
I‘d like to handle this enhancement |
For me the notification lists dependants. #104997 added the ability to disable the dependants directly from the notification that appears when disabling (rather than uninstalling). Sounds like we want the same on the uninstall. |
the notification lists 2 dependants at most. This is insufficient data. |
Fair point. But as a workaround you can presumably uninstall the two shown, then try again on the main extension and find out which two (or possibly one) to uninstall next. |
Yes, but I get @fbricon‘s point. Installing every single extension by hand, and rechecking dependencies after removing the two removed extensions by may be kind of annoying. |
I am unclear who "you" is. |
I was referring to @fbricon |
I think we provide |
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! |
To verify:
|
A user reported that he "Cannot uninstall 'Language Support for Java(TM) by Red Hat' extension. 'Java Test Runner' extension depends on this.", but it's only one extension among many that depend on Java.
Rather than manually hunting down those extensions to uninstall first (which itself is a daunting task, see #119242), the warning popup should provide a button to uninstall all those other extensions (and their dependants) as well.
See redhat-developer/vscode-java#1837
The text was updated successfully, but these errors were encountered: