aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/README.md7
-rw-r--r--docs/dev/lsp-extensions.md8
2 files changed, 9 insertions, 6 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 6b6824ded..f87462400 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -177,6 +177,9 @@ There are many benefits to this:
177* less stuff printed during printf-debugging 177* less stuff printed during printf-debugging
178* less time to run test 178* less time to run test
179 179
180It also makes sense to format snippets more compactly (for example, by placing enum defitions like `enum E { Foo, Bar }` on a single line),
181as long as they are still readable.
182
180## Order of Imports 183## Order of Imports
181 184
182We separate import groups with blank lines 185We separate import groups with blank lines
@@ -358,10 +361,10 @@ There are two kinds of tests:
358The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for. 361The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for.
359If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test. 362If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test.
360 363
361To update test data, run with `UPDATE_EXPECTATIONS` variable: 364To update test data, run with `UPDATE_EXPECT` variable:
362 365
363```bash 366```bash
364env UPDATE_EXPECTATIONS=1 cargo qt 367env UPDATE_EXPECT=1 cargo qt
365``` 368```
366 369
367After adding a new inline test you need to run `cargo xtest codegen` and also update the test data as described above. 370After adding a new inline test you need to run `cargo xtest codegen` and also update the test data as described above.
diff --git a/docs/dev/lsp-extensions.md b/docs/dev/lsp-extensions.md
index a0847dad3..c0afb16d3 100644
--- a/docs/dev/lsp-extensions.md
+++ b/docs/dev/lsp-extensions.md
@@ -389,15 +389,15 @@ rust-analyzer supports only one `kind`, `"cargo"`. The `args` for `"cargo"` look
389 389
390Returns internal status message, mostly for debugging purposes. 390Returns internal status message, mostly for debugging purposes.
391 391
392## Collect Garbage 392## Reload Workspace
393 393
394**Method:** `rust-analyzer/collectGarbage` 394**Method:** `rust-analyzer/reloadWorkspace`
395 395
396**Request:** `null` 396**Request:** `null`
397 397
398**Response:** `null` 398**Response:** `null`
399 399
400Frees some caches. For internal use, and is mostly broken at the moment. 400Reloads project information (that is, re-executes `cargo metadata`).
401 401
402## Syntax Tree 402## Syntax Tree
403 403
@@ -504,4 +504,4 @@ Such actions on the client side are appended to a hover bottom as command links:
504 | TITLE _Action1_ | _Action2_ | <- second group 504 | TITLE _Action1_ | _Action2_ | <- second group
505 +-----------------------------+ 505 +-----------------------------+
506 ... 506 ...
507``` \ No newline at end of file 507```