Start on any Smithy files (smithy-lang#96)

Previous behavior was for the extension to be triggered when you opened
a `.smithy` file. This commit makes the extension trigger whenever
there's a smithy file (or build file) in the workspace.

package.json

@@ -22,6 +22,11 @@
   ],
   "main": "./out/src/extension",
   "preview": true,
+  "activationEvents": [
+    "workspaceContains:**/smithy-build.json",
+    "workspaceContains:**/*.smithy",
+    "workspaceContains:**/.smithy-project.json"
+  ],
   "contributes": {
     "jsonValidation": [
       {

test-fixtures/suite6/smithy-build.json

@@ -0,0 +1,3 @@
+{
+  "version": "1.0"
+}

tests/runTest.ts

@@ -48,6 +48,13 @@ async function go() {
       launchArgs: [resolve(__dirname, "../../test-fixtures/suite5")],
     });
 
+    // Suite 6 - Startup
+    await runTests({
+      extensionDevelopmentPath,
+      extensionTestsPath: resolve(__dirname, "./suite6"),
+      launchArgs: [resolve(__dirname, "../../test-fixtures/suite6")],
+    });
+
     // Confirm that webpacked and vsce packaged extension can be installed.
     const vscodeExecutablePath = await downloadAndUnzipVSCode();
     const [cli, ...args] = resolveCliArgsFromVSCodeExecutablePath(vscodeExecutablePath);

tests/suite6/extension.test.ts

@@ -0,0 +1,13 @@
+import * as assert from "assert";
+import * as vscode from "vscode";
+
+suite("Startup", function () {
+  this.timeout(0);
+
+  test("Should start without opening a smithy file", async () => {
+    const extension = vscode.extensions.getExtension("smithy.smithy-vscode-extension");
+    assert.ok(extension.isActive);
+
+    return Promise.resolve();
+  });
+});

tests/suite6/index.ts

@@ -0,0 +1,5 @@
+import { runTests } from "../helper";
+
+export function run(testsRoot: string, cb: (error: any, failures?: number) => void): void {
+  runTests(testsRoot, cb);
+}