Skip to content

fix: include disabled extensions in sync to prevent deletion - #1473

Open
dev-khimesh wants to merge 1 commit into
shanalikhan:masterfrom
dev-khimesh:fix/143-disabled-extensions
Open

fix: include disabled extensions in sync to prevent deletion#1473
dev-khimesh wants to merge 1 commit into
shanalikhan:masterfrom
dev-khimesh:fix/143-disabled-extensions

Conversation

@dev-khimesh

Copy link
Copy Markdown

Description

Fixes #143 — disabled VS Code extensions are no longer excluded from sync. Previously, \ only returns enabled extensions, causing disabled ones to be omitted from the gist and potentially deleted during download on another machine.

Changes

  • Added \ flag to \ class
  • Added \ to read all installed extensions from disk
  • Added \ to parse \ folder names
  • Modified \ to include extensions found on disk but not in \ (i.e., disabled extensions)

Conservative Approach

This is a conservative fix that only prevents disabled extensions from being deleted during sync. It does not attempt to restore disabled/reenable state across machines, as VS Code does not expose a reliable API for this.

Closes #143

Adds support for syncing disabled VS Code extensions. Previously, disabled extensions were excluded from vscode.extensions.all, causing them to be absent from the gist and potentially deleted during download.

Changes:
- Added disabled flag to ExtensionInformation class
- Added ScanExtensionsFolder() to read extensions directory on disk
- Added ParseExtensionFolderName() for folder name parsing
- Modified CreateExtensionList() to include disabled extensions found on disk

Closes shanalikhan#143
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Considering disabled extensions

1 participant