aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/lsp-extensions.md
Commit message (Collapse)AuthorAgeFilesLines
* Update lsp-extensions.mdJonas Schievink2021-05-211-2/+18
|
* feat: allow clients to feature detect symbol filteringAleksey Kladov2021-05-191-12/+16
|
* Add new LSP extension for workspace symbol lookupalcroito2021-05-171-1/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config.
* Document viewCrateGraph requestJonas Schievink2021-05-111-1/+11
|
* Remove confusion around serverStatusNotificationAleksey Kladov2021-04-191-3/+8
|
* Fix spec bugAleksey Kladov2021-04-191-1/+1
|
* Update lsp-extensions docsLukas Wirth2021-04-181-1/+2
|
* Move cursor position when using item moversJonas Schievink2021-04-131-3/+3
|
* Small grammar fixesKirill Bulatov2021-04-061-7/+7
|
* More robust status notificationsAleksey Kladov2021-04-061-8/+22
|
* docs: Fix moveItem method namesim2021-04-041-2/+1
|
* Item up and down moversivan7702021-03-181-1/+27
|
* Merge #7799bors[bot]2021-03-131-1/+17
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7799: Related tests r=matklad a=vsrs ![tests](https://user-images.githubusercontent.com/62505555/109397453-a9013680-7947-11eb-8b11-ac03079f7645.gif) This adds an ability to look for tests for the item under the cursor: function, constant, data type, etc The LSP part is bound to change. But the feature itself already works and I'm looking for a feedback :) Co-authored-by: vsrs <[email protected]>
| * Fix LSP extensions documentationvsrs2021-03-111-7/+2
| |
| * Update lsp-extensions.mdvsrs2021-02-271-1/+22
| |
* | Clarify that all caps are experimentalAleksey Kladov2021-03-091-10/+10
|/
* document offsetsAleksey Kladov2021-02-161-1/+7
|
* Remove CodeLensResolveData mention from lsp-extensions.mdivan7702021-02-131-11/+0
|
* Moved CodeLens to ide crateivan7702021-02-131-1/+12
|
* fix nightly warning `legacy_derive_helpers`Peter Wischer2021-02-121-1/+1
| | | | see https://github.com/rust-lang/rust/issues/79202
* Fix spelling mistakes in docs/devLukas Wirth2021-02-031-1/+1
|
* Update lsp-extension.md hashEdwin Cheng2021-01-281-1/+1
|
* Update docEdwin Cheng2021-01-281-1/+1
|
* Address review suggestion, fix tidy testsPhil Ellison2021-01-011-1/+12
|
* 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.
* Document change of 'cargo' Runnable kind in lsp-extensions.mdIgor Aleksanov2020-10-161-0/+3
|
* 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
|
* Extend **Status** command to also show dep info for the fileAleksey Kladov2020-09-291-1/+8
| | | | This should help with troubleshooting wrong project configuration
* Fix StatusNotificationvsrs2020-08-171-1/+7
|
* SSR: Pass current file position through to SSR code.David Lattimore2020-07-241-1/+6
| | | | In a subsequent commit, it will be used for resolving paths.
* Clarify initializationOptionsJeremy Kolb2020-07-221-3/+5
|
* Implement StatusBarAleksey Kladov2020-07-021-0/+12
|
* Add reload workspace commandAleksey Kladov2020-07-011-4/+4
|
* Add hover actions LSP extension documentation.vsrs2020-06-051-0/+38
|
* Add documentationMikhail Rakhmanov2020-06-031-0/+24
|
* Spec better runnablesAleksey Kladov2020-06-021-36/+44
|
* Merge #4580bors[bot]2020-06-021-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | 4580: Fix invoking cargo without consulting CARGO env var or standard installation paths r=matklad a=Veetaha Followup for #4329 The pr essentially fixes [this bug](https://youtu.be/EzQ7YIIo1rY?t=2189) cc @lefticus Co-authored-by: veetaha <[email protected]>
| * Change Runnable.bin -> Runnable.kindveetaha2020-05-311-1/+1
| | | | | | | | | | | | As per matklad, we now pass the responsibility for finding the binary to the frontend. Also, added caching for finding the binary path to reduce the amount of filesystem interactions.
* | Subscribe to protocol changesAleksey Kladov2020-06-011-0/+2
| |
* | Document initilizationOptions used by rust-analyzerAleksey Kladov2020-06-011-0/+8
|/
* Fix typo in docs/dev/lsp-extensions.md: automagiacally -> automagicallyStephan Seitz2020-05-291-1/+1
|
* typoVeetaha2020-05-271-1/+1
|
* Document inlay hints and runnablesAleksey Kladov2020-05-271-0/+63
| | | | We want to change those, but let's document what we have in meantime
* Document `parentModule` experimental LSP requestAleksey Kladov2020-05-251-5/+35
|
* Cleanup lsp extensions on the client sideAleksey Kladov2020-05-251-1/+1
|
* Less rust-analyzer specific onEnterAleksey Kladov2020-05-251-0/+53
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 02:04:29 +0000