Add codesearch feature (#33)

Integrates Bzl codeesearch with the vscode extension

Author: pcj

.gitignore

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

.vscode/extensions.json

@@ -0,0 +1 @@
+{}

.vscode/launch.json

@@ -0,0 +1,36 @@
+// A launch configuration that compiles the extension and then opens it inside a new window
+// Use IntelliSense to learn about possible attributes.
+// Hover to view descriptions of existing attributes.
+// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+{
+	"version": "0.2.0",
+	"configurations": [
+		{
+			"name": "Run Extension",
+			"type": "extensionHost",
+			"request": "launch",
+			"runtimeExecutable": "${execPath}",
+			"args": [
+				"--extensionDevelopmentPath=${workspaceFolder}"
+			],
+			"outFiles": [
+				"${workspaceFolder}/out/**/*.js"
+			],
+			"preLaunchTask": "${defaultBuildTask}"
+		},
+		{
+			"name": "Extension Tests",
+			"type": "extensionHost",
+			"request": "launch",
+			"runtimeExecutable": "${execPath}",
+			"args": [
+				"--extensionDevelopmentPath=${workspaceFolder}",
+				"--extensionTestsPath=${workspaceFolder}/out/test/suite/index"
+			],
+			"outFiles": [
+				"${workspaceFolder}/out/test/**/*.js"
+			],
+			"preLaunchTask": "${defaultBuildTask}"
+		}
+	]
+}

.vscode/settings.json

@@ -0,0 +1,11 @@
+// Place your settings in this file to overwrite default and user settings.
+{
+    "files.exclude": {
+        "out": false // set this to true to hide the "out" folder with the compiled JS files
+    },
+    "search.exclude": {
+        "out": true // set this to false to include "out" folder in search results
+    },
+    // Turn off tsc task auto detection since we have the necessary tasks as npm scripts
+    "typescript.tsc.autoDetect": "off"
+}

.vscode/tasks.json

@@ -0,0 +1,20 @@
+// See https://go.microsoft.com/fwlink/?LinkId=733558
+// for the documentation about the tasks.json format
+{
+	"version": "2.0.0",
+	"tasks": [
+		{
+			"type": "npm",
+			"script": "watch",
+			"problemMatcher": "$tsc-watch",
+			"isBackground": true,
+			"presentation": {
+				"reveal": "never"
+			},
+			"group": {
+				"kind": "build",
+				"isDefault": true
+			}
+		}
+	]
+}

docs/searching.md

@@ -0,0 +1,37 @@
+---
+layout: default
+title: Searching
+permalink: /searching
+nav_order: 5
+---
+
+## Codesearch
+
+<p></p>
+
+The codesearch feature allows one to:
+
+1. create a search index of source files
+defined by a bazel query
+1. query the index (optionally with regular expressions).
+
+To define a codesearch index, add a line to your `launch.bazelrc` such as:
+
+```
+codesearch deps(//...)
+```
+
+Upon save, vscode will add two *code lenses* above the line:
+
+![codesearch-define](https://user-images.githubusercontent.com/50580/96071853-3abc4b80-0e60-11eb-8d3b-897004d5bd8c.gif)
+
+- To (re-)create the index, click the `Index` lens.
+- To search, click the `Search` lens.
+- Click on a matching line to nagivate to the file.
+
+Display of the code lenses is dependent on knowing which bazel workspace you are
+operating within, so if you don't see them after opening your `launch.bazelrc`
+file, open the Bazel activity view pane.
+
+> Note that you are responsible for updating the index manually, there isn't
+currently a way to have the index automatically be updated.