Bzl integration (#25)

Author: pcj

.gitignore

@@ -1,4 +1,6 @@
 out
+tmp
 node_modules
+.vscode
 .vscode-test/
 *.vsix

.vscode/extensions.json

@@ -2,10 +2,11 @@
 .vscode-test/**
 out/test/**
 src/**
+tmp/**
+docs/**
 .gitignore
-ext.vsix
-vsc-extension-quickstart.md
 **/tsconfig.json
 **/.eslintrc.json
 **/*.map
 **/*.ts
+node_modules/**

.vscode/launch.json

@@ -1,5 +1,9 @@
 # Change Log
 
+## 0.5.0 (Thu Set 17 2020)
+
+- Experimental Bzl integration (disabled by default)
+
 ## 0.4.1 (Tue Aug 4 2020)
 
 - Enable language server by default

.vscode/settings.json

@@ -98,7 +98,7 @@ Build and test targets quickly within vscode.
 
 Quick-pick targets and jump to their location.
 
-![bzl-repositories](https://user-images.githubusercontent.com/50580/93265314-b2199500-f765-11ea-903e-b00600a1f2df.gif)
+![bsv.bzl.repository](https://user-images.githubusercontent.com/50580/93265314-b2199500-f765-11ea-903e-b00600a1f2df.gif)
 
 ### Bzl Integration
 

.vscode/tasks.json

@@ -24,7 +24,7 @@ This is due to several possible root causes:
    delete the `output_base`.
 3. You have a non-standard location where you are persisting output bases,
    perhaps with the `--output_user_root` flag.  To fix, configure the
-   `feature.bzl.server.command` extension setting to include the flag
+   `bsv.bzl.server.command` extension setting to include the flag
    `--repository_output_user_root=/path/to/output_user_root`.  This will allow
    bzl to scan subdirectories of this location.
 4. A bug in Bzl that prevented it from finding your repositories.
@@ -34,5 +34,9 @@ Additional steps to resolve this issue:
 1. Start vscode in a bazel repository.
 2. Explicitly configure the location of bazel repositories on your filesystem.
    To fix, configure the
-   `feature.bzl.server.command` extension setting to include the flag
+   `bsv.bzl.server.command` extension setting to include the flag
    `--repository_dir=/path/to/bazel_repo`.
+3. Enable debug logging for the bzl server with `--log_level=debug` (or
+   `--log_level=workspace=debug` to be more selective) in
+   `bsv.bzl.server.command`.
+

.vscodeignore

@@ -0,0 +1,62 @@
+
+�
+git_repository�Clone an external git repository.
+
+Clones a Git repository, checks out the specified tag, or commit, and
+makes its targets available for binding. Also determine the id of the
+commit actually checked out and its date, and return a dict with parameters
+that provide a reproducible version of this rule (which a tag not necessarily
+is).
+.
+name"A unique name for this repository.
 
z
+branchjbranch in the remote repository to checked out. Precisely one of branch, tag, or commit must be specified.2""m
+commit]specific commit to be checked out. Precisely one of branch, tag, or commit must be specified.2""J
+init_submodules.Whether to clone submodules in the repository.2False�
+
+patch_args�The arguments given to the patch tool. Defaults to -p0, however -p1 will usually be needed for patches generated by git. If multiple -p arguments are specified, the last one will take effect.If arguments other than -p are specified, Bazel will fall back to use patch command line tool instead of the Bazel-native patch implementation. When falling back to patch command line tool and patch_tool attribute is not specified, `patch` will be used.2["-p0"]e
+
+patch_cmdsQSequence of Bash commands to be applied on Linux/Macos after patches are applied.2[]�

+patch_cmds_win�
Sequence of Powershell commands to be applied on Windows after patches are applied. If this attribute is not set, patch_cmds will be executed on Windows, which requires Bash binary to exist.2[]�

+
+patch_tool�
The patch(1) utility to use. If this is specified, Bazel will use the specifed patch tool instead of the Bazel-native patch implementation.2""�
+patches�A list of files that are to be applied as patches after extracting the archive. By default, it uses the Bazel-native patch implementation which doesn't support fuzz match and binary patch, but Bazel will fall back to use patch command line tool if `patch_tool` attribute is specified or there are arguments other than `-p` in `patch_args` attribute.2[]2
+remote$The URI of the remote Git repository 
�
+repo_mapping�A dictionary from local repository name to global repository name. This allows controls over workspace dependency resolution for dependencies of this repository.<p>For example, an entry `"@foo": "@bar"` declares that, for any time this repository depends on `@foo` (such as a dependency on `@foo//some:target`, it should actually resolve that dependency within globally-declared `@bar` (`@bar//some:target`).
+ 
�
+shallow_since�an optional date, not after the specified commit; the argument is not allowed if a tag is specified (which allows cloning with depth 1). Setting such a date close to the specified commit allows for a more shallow clone of the repository, saving bandwidth and wall-clock time.2""K
+strip_prefix5A directory prefix to strip from the extracted files.2""t
+taggtag in the remote repository to checked out. Precisely one of branch, tag, or commit must be specified.2""
+verbose2False
+�
+new_git_repository�Clone an external git repository.
+
+Clones a Git repository, checks out the specified tag, or commit, and
+makes its targets available for binding. Also determine the id of the
+commit actually checked out and its date, and return a dict with parameters
+that provide a reproducible version of this rule (which a tag not necessarily
+is).
+.
+name"A unique name for this repository.
 
z
+branchjbranch in the remote repository to checked out. Precisely one of branch, tag, or commit must be specified.2""�
+
+build_file�The file to use as the BUILD file for this repository.This attribute is an absolute label (use '@//' for the main repo). The file does not need to be named BUILD, but can be (something like BUILD.new-repo-name may work well for distinguishing it from the repository's actual BUILD files. Either build_file or build_file_content must be specified.2None�

+build_file_contentnThe content for the BUILD file for this repository. Either build_file or build_file_content must be specified.2""m
+commit]specific commit to be checked out. Precisely one of branch, tag, or commit must be specified.2""J
+init_submodules.Whether to clone submodules in the repository.2False�
+
+patch_args�The arguments given to the patch tool. Defaults to -p0, however -p1 will usually be needed for patches generated by git. If multiple -p arguments are specified, the last one will take effect.If arguments other than -p are specified, Bazel will fall back to use patch command line tool instead of the Bazel-native patch implementation. When falling back to patch command line tool and patch_tool attribute is not specified, `patch` will be used.2["-p0"]e
+
+patch_cmdsQSequence of Bash commands to be applied on Linux/Macos after patches are applied.2[]�

+patch_cmds_win�
Sequence of Powershell commands to be applied on Windows after patches are applied. If this attribute is not set, patch_cmds will be executed on Windows, which requires Bash binary to exist.2[]�

+
+patch_tool�
The patch(1) utility to use. If this is specified, Bazel will use the specifed patch tool instead of the Bazel-native patch implementation.2""�
+patches�A list of files that are to be applied as patches after extracting the archive. By default, it uses the Bazel-native patch implementation which doesn't support fuzz match and binary patch, but Bazel will fall back to use patch command line tool if `patch_tool` attribute is specified or there are arguments other than `-p` in `patch_args` attribute.2[]2
+remote$The URI of the remote Git repository 
�
+repo_mapping�A dictionary from local repository name to global repository name. This allows controls over workspace dependency resolution for dependencies of this repository.<p>For example, an entry `"@foo": "@bar"` declares that, for any time this repository depends on `@foo` (such as a dependency on `@foo//some:target`, it should actually resolve that dependency within globally-declared `@bar` (`@bar//some:target`).
+ 
�
+shallow_since�an optional date, not after the specified commit; the argument is not allowed if a tag is specified (which allows cloning with depth 1). Setting such a date close to the specified commit allows for a more shallow clone of the repository, saving bandwidth and wall-clock time.2""K
+strip_prefix5A directory prefix to strip from the extracted files.2""t
+taggtag in the remote repository to checked out. Precisely one of branch, tag, or commit must be specified.2""
+verbose2False�

+workspace_file�
The file to use as the `WORKSPACE` file for this repository. Either `workspace_file` or `workspace_file_content` can be specified, or neither, but not both.2None�

+workspace_file_content�
The content for the WORKSPACE file for this repository. Either `workspace_file` or `workspace_file_content` can be specified, or neither, but not both.2""*,Rules for cloning external git repositories.