You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just faced a strange behavior.
A user already installed a private extension 'A', then disable it in extensions view.
Few month later, he came back in Private extension list, and see the button install under the extension A.
Click on it, but nothing change.
Finally he discover that the extension was disabled.
To sumup: When a private extension is disabled, the user has access to the button Install that does nothing.
It could be better instead to remove this button, and add the button enable instead.
Thanks :)
The text was updated successfully, but these errors were encountered:
I'd have to investigate further, but it sounds like this may simply be a limitation of the extensions API that extensions.all does not provide info for disabled extensions. I don't see any way in the API to determine if an extension is enabled or disabled, so I suspect you just can't access any information about disabled extensions.
I checked a bit the documetation and perfomed some quick test. indeed the API is limited.
The only way to know if an extension is disabled is to compare the output of code --list-extensions (it returns all installed extensions) and the extensions.all (returns only the activated extensions).
or used the function vscode.extensions.getExtension('') which returns undefined when an extension is installed and disabled.
Hello,
We just faced a strange behavior.
A user already installed a private extension 'A', then disable it in extensions view.
Few month later, he came back in Private extension list, and see the button install under the extension A.
Click on it, but nothing change.
Finally he discover that the extension was disabled.
To sumup: When a private extension is disabled, the user has access to the button Install that does nothing.
It could be better instead to remove this button, and add the button enable instead.
Thanks :)
The text was updated successfully, but these errors were encountered: