feat: credo lsp

Author: mhanberg

README.md

@@ -1,71 +1,9 @@
-# elixir-tools.vscode README
+# elixir-tools.vscode
 
-This is the README for your extension "elixir-tools.vsocde". After writing up a brief description, we recommend including the following sections.
+The official [elixir-tools](https://github.com/elixir-tools) extension for VSCode!
 
-## Features
+elixir-tools.vscode provides support for:
 
-Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
-
-For example if there is an image subfolder under your extension project workspace:
-
-\!\[feature X\]\(images/feature-x.png\)
-
-> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
-
-## Requirements
-
-If you have any requirements or dependencies, add a section describing those and how to install and configure them.
-
-## Extension Settings
-
-Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
-
-For example:
-
-This extension contributes the following settings:
-
-* `myExtension.enable`: Enable/disable this extension.
-* `myExtension.thing`: Set to `blah` to do something.
-
-## Known Issues
-
-Calling out known issues can help limit users opening duplicate issues against your extension.
-
-## Release Notes
-
-Users appreciate release notes as you update your extension.
-
-### 1.0.0
-
-Initial release of ...
-
-### 1.0.1
-
-Fixed issue #.
-
-### 1.1.0
-
-Added features X, Y, and Z.
-
----
-
-## Following extension guidelines
-
-Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.
-
-* [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
-
-## Working with Markdown
-
-You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
-
-* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux).
-* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux).
-* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets.
-
-## For more information
-
-* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
-* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
-
-**Enjoy!**
+* Filetype detection for .ex and .exs Elixir files
+* Syntax highlight for Elixir
+* Credo Language Server

package.json

@@ -12,6 +12,16 @@
   "activationEvents": [],
   "main": "./dist/extension.js",
   "contributes": {
+    "configuration": {
+      "title": "elixir-tools",
+      "properties": {
+        "elixir-tools.credo.enabled": {
+          "type": "boolean",
+          "default": true,
+          "description": "Whether to start the Credo Language Server."
+        }
+      }
+    },
     "languages": [
       {
         "id": "elixir",

src/extension.ts

@@ -1,46 +1,48 @@
-// The module 'vscode' contains the VS Code extensibility API
-// Import the module and reference it with the alias vscode in your code below
 import * as vscode from "vscode";
-// import { workspace } from "vscode";
 
 import {
   Executable,
   LanguageClient,
   LanguageClientOptions,
 } from "vscode-languageclient/node";
 
-let client: LanguageClient;
-
-// This method is called when your extension is activated
-// Your extension is activated the very first time the command is executed
-export function activate(_context: vscode.ExtensionContext) {
-  // Options to control the language client
-  //
-  const serverOptions: Executable = {
-    command: "mix",
-    args: ["credo.lsp", "--stdio"],
-  };
-  const clientOptions: LanguageClientOptions = {
-    // Register the server for plain text documents
-    documentSelector: [{ scheme: "file", language: "elixir" }],
-  };
-
-  // Create the language client and start the client.
-  client = new LanguageClient(
-    "elixir-tools.credo",
-    "Credo",
-    serverOptions,
-    clientOptions
-  );
-
-  // Start the client. This will also launch the server
-  client.start();
+let credoClient: LanguageClient;
+
+export async function activate(_context: vscode.ExtensionContext) {
+  let files = await vscode.workspace.findFiles("mix.exs");
+
+  let config = vscode.workspace.getConfiguration("elixir-tools.credo");
+
+  if (files[0]) {
+    let text = await vscode.workspace.fs.readFile(files[0]);
+
+    if (text.toString().includes("{:credo")) {
+      if (config.get("enabled")) {
+        const serverOptions: Executable = {
+          command: "mix",
+          args: ["credo.lsp", "--stdio"],
+        };
+        const clientOptions: LanguageClientOptions = {
+          documentSelector: [{ scheme: "file", language: "elixir" }],
+        };
+
+        credoClient = new LanguageClient(
+          "elixir-tools.credo",
+          "Credo",
+          serverOptions,
+          clientOptions
+        );
+
+        // Start the credoClient. This will also launch the server
+        credoClient.start();
+      }
+    }
+  }
 }
 
-// This method is called when your extension is deactivated
 export function deactivate() {
-  if (!client) {
+  if (!credoClient) {
     return undefined;
   }
-  return client.stop();
+  return credoClient.stop();
 }