Update for VS Code 1.26 #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
August 14, 2018 17:59
Use "extensionPack" instead of "extensionDependencies" in package.json. This will make it much simpler and easier for users to manage an Extension Pack and its bundled extensions. It allows deactivating and uninstalling extensions installed by the extension pack without affecting the extension pack itself. See https://code.visualstudio.com/updates/v1_26#_extension-packs-revisited
VS Code already provides intellisense for paths.
|
thnks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
extensionPackinstead ofextensionDependenciesinpackage.json.As per the VS Code 1.26 release notes "[t]his will make it much simpler and easier for users to manage an Extension Pack and its bundled extensions. It allows deactivating and uninstalling extensions installed by the extension pack without affecting the extension pack itself."
"An Extension Pack should not have any functional dependencies with its bundled extensions and they should be manageable independent of the pack." "This needs adoption by Extension Packs":
Since I don't have any experience in developing VS Code extensions I wasn't able to successfully test this on my machine. Pressing
F5as described in thevsc-extension-quickstart.mdworked but didn't show the expected results.The
extensionPackfeature had been discussed in microsoft/vscode#48430Can anyone please confirm this is working? What about downwards compatibility?
Resolves #10