From e18661f62b884ba970f8b3267400bf4320c7b118 Mon Sep 17 00:00:00 2001 From: Veetaha Date: Sun, 9 Feb 2020 20:19:23 +0200 Subject: docs: Freshen docs for prebuilt binaries and raLspServer setting --- docs/dev/README.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'docs/dev') diff --git a/docs/dev/README.md b/docs/dev/README.md index 732e4bdd3..991deaf90 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -74,7 +74,7 @@ relevant test and execute it (VS Code includes an action for running a single test). However, launching a VS Code instance with locally build language server is -possible. There's "Run Extension (Dev Server)" launch configuration for this. +possible. There's **"Run Extension (Dev Server)"** launch configuration for this. In general, I use one of the following workflows for fixing bugs and implementing features. @@ -88,7 +88,14 @@ Code to sanity check that the thing works as I expect. If the problem concerns only the VS Code extension, I use **Run Extension** launch configuration from `launch.json`. Notably, this uses the usual -`ra_lsp_server` binary from `PATH`. After I am done with the fix, I use `cargo +`ra_lsp_server` binary from `PATH`. For this it is important to have the following +in `setting.json` file: +```json +{ + "rust-analyzer.raLspServerPath": "ra_lsp_server" +} +``` +After I am done with the fix, I use `cargo xtask install --client-code` to try the new extension for real. If I need to fix something in the `ra_lsp_server` crate, I feel sad because it's -- cgit v1.2.3