vscode-with-extension: improvements

-  Now simply let the default `unpackPhase` unzip the vsix file. This
    should allow users to retrieve the extension directly from github.
 -  Extensions now installed using their unique id as install folder.
 -  Extensions under `vscode-extensions` now use the unique id
    as extension name.
This commit is contained in:
Raymond Gauthier
2017-08-23 21:31:57 -04:00
parent d3532906da
commit 763f7f7578
3 changed files with 30 additions and 34 deletions
+12 -5
View File
@@ -3,16 +3,23 @@
let
inherit (vscode-utils) buildVscodeExtension buildVscodeMarketplaceExtension;
in
#
# Unless there is a good reason not to, we attemp to use the same name as the
# extension's unique identifier (the name the extension gets when installed
# from vscode under `~/.vscode`) and found on the marketplace extension page.
# So an extension's attribute name should be of the form:
# "${mktplcRef.publisher}.${mktplcRef.name}".
#
rec {
nix = buildVscodeMarketplaceExtension {
bbenoist.Nix = buildVscodeMarketplaceExtension {
mktplcRef = {
name = "nix";
name = "Nix";
publisher = "bbenoist";
version = "1.0.1";
sha256 = "0zd0n9f5z1f0ckzfjr38xw2zzmcxg1gjrava7yahg5cvdcw6l35b";
};
# TODO: Fill meta with appropriate information.
meta = with stdenv.lib; {
license = licenses.mit;
};
};
}