aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* fix typo of README in devDaiki Ihara2020-12-081-1/+1
|
* Document statelessness invariantAleksey Kladov2020-12-031-0/+16
|
* More accurately place proc-macro diagnosticJonas Schievink2020-11-271-1/+1
|
* Publish diagnostics for macro expansion errorsJonas Schievink2020-11-271-0/+14
|
* fix typos in syntax.mdJakob Hellermann2020-11-171-2/+2
|
* Latest LSP 3.16 protocolkjeremy2020-11-161-2/+2
| | | | Pulls in https://github.com/gluon-lang/lsp-types/pull/186
* add open Cargo.toml actionAnatol Liu2020-11-131-2/+27
|
* Switch to upstream protocol for resolving code actionAleksey Kladov2020-11-101-25/+1
| | | | | | Note that we have to maintain custom implementation on the client side: I don't see how to marry bulitin resolve support with groups and snippets.
* don\t indent testsAleksey Kladov2020-11-061-0/+26
|
* Update docs/dev/style.mdAleksey Kladov2020-11-021-1/+1
| | | Co-authored-by: Laurențiu Nicola <[email protected]>
* Document doer object anti-patternAleksey Kladov2020-11-021-0/+54
|
* docs: Update Neovim nvim-lspconfig repository linkDave Lage2020-10-291-2/+2
|
* Update client install command in dev docsLaurențiu Nicola2020-10-271-1/+1
|
* Fix name of InactiveCode diagnosticJonas Schievink2020-10-231-6/+6
|
* Diagnose #[cfg]s in bodiesJonas Schievink2020-10-231-4/+4
|
*-. Merge #6325 #6327bors[bot]2020-10-222-1/+8
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6325: Add generated diagnostic docs to the manual r=matklad a=flodiebold It seemed that we're not actually including the generated diagnostic docs anywhere yet? So I added something to the manual. This is completely untested though. 6327: Update debugging.md r=matklad a=stanciuadrian `on_task` is no longer there. I have used `on_request` instead. Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Adrian Stanciu <[email protected]>
| | * Update debugging.mdAdrian Stanciu2020-10-221-1/+1
| |/ |/|
| * Add generated diagnostic docs to the manualFlorian Diebold2020-10-221-0/+7
|/
* add completions for clippy lint in attributesBenjamin Coenen2020-10-201-0/+105
| | | | Signed-off-by: Benjamin Coenen <[email protected]>
* Support Display name in project.jsonAleksey Kladov2020-10-201-0/+3
|
* Document logging of project modelAleksey Kladov2020-10-191-0/+1
|
* Document change of 'cargo' Runnable kind in lsp-extensions.mdIgor Aleksanov2020-10-161-0/+3
|
* Merge #6245bors[bot]2020-10-161-10/+1
|\ | | | | | | | | | | | | | | 6245: Update GNOME Builder docs r=lnicola a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * Update GNOME Builder docsLaurențiu Nicola2020-10-151-10/+1
| |
* | Expand code order sectionAleksey Kladov2020-10-161-11/+50
|/
* Document awkward namesAleksey Kladov2020-10-151-0/+12
|
* Cleanup alloc adviceAleksey Kladov2020-10-151-0/+7
|
* Style: default over newAleksey Kladov2020-10-141-0/+25
|
* Introduce S-actionable and S-unactionable labelsAleksey Kladov2020-10-141-1/+6
| | | | | | | | | | I've noticed that a significant fraction of issues are inert. They are valid, acknowledged and useful, but effectively can't be fixed for variety of reasons (no reproduction, dependencies on some other issues, no review capacity, etc). Marking issues that can be fixed by just applying some elbow grease seems useful!
* Add reminder to update lsp-extensions.mdAleksey Kladov2020-10-141-0/+10
|
* Fix send->sent typoZac Pullar-Strecker2020-10-081-7/+7
|
* Document the protocol extensionZac Pullar-Strecker2020-10-081-1/+12
|
* minorAleksey Kladov2020-10-071-1/+1
|
* minorAleksey Kladov2020-10-071-11/+11
|
* Add comparisons guideline to styleAleksey Kladov2020-10-071-0/+27
|
* Reorg styleAleksey Kladov2020-10-071-176/+181
|
* Update manual.adocAdrian Stanciu2020-10-061-0/+17
|
* Document Clippy strategyAleksey Kladov2020-10-021-0/+10
|
* Improve grammar and fix code example in style guideLaurențiu Nicola2020-10-011-5/+4
|
* Extend **Status** command to also show dep info for the fileAleksey Kladov2020-09-292-3/+10
| | | | This should help with troubleshooting wrong project configuration
* More style adviceAleksey Kladov2020-09-291-0/+52
|
* VS Code + WSL: describe binary locationMasaki Hara2020-09-211-0/+1
| | | It looks like VS Code server chooses a different location for `globalStorage`.
* Fix typoYusuke Tanaka2020-09-201-1/+1
|
* Fix typoYusuke Tanaka2020-09-201-1/+1
|
* docs: suggest disabling the official extensionJonas Schievink2020-09-181-0/+5
|
* fmt importAleksey Kladov2020-08-281-0/+16
|
* Merge #5879bors[bot]2020-08-261-5/+3
|\ | | | | | | | | | | | | | | | | 5879: Update mentions of 'ra_vfs' in architecture doc r=matklad a=rherrmann Adjust the paragraph about `ra_vfs` to point to the `vfs` crate that is used now. Co-authored-by: Rüdiger Herrmann <[email protected]>
| * Update mentions of 'ra_vfs' in architecture docRüdiger Herrmann2020-08-251-5/+3
| | | | | | Adjust the paragraph about `ra_vfs` to point to the `vfs` crate that is used now.
* | Merge #5885bors[bot]2020-08-261-0/+24
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5885: Make inlay hints colors more configurable r=matklad a=Veetaha **[BREAKING CHANGE]** Tackles https://github.com/rust-analyzer/rust-analyzer/issues/5337#issuecomment-680018601 and generally related to #5337. Added `foreground/background` color configurations with optional more specific overrides `foreground.(type|parameter|chaining)Hints`. One problem I see is that the config keys are long and don't fit into the on-hover hints in the `settings.json` file entirely... <details> <summary>Demo</summary> ![demo](https://user-images.githubusercontent.com/36276403/91238334-77fc3b00-e745-11ea-836b-2822015ece98.gif) </details> Co-authored-by: Veetaha <[email protected]>
| * | Make inlay hints colors more configurableVeetaha2020-08-261-0/+24
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 23:06:03 +0000