aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server/src/main_loop.rs
Commit message (Collapse)AuthorAgeFilesLines
...
* cleanupAleksey Kladov2019-05-311-35/+48
|
* simplifyAleksey Kladov2019-05-311-51/+52
|
* move completed requests to a separate fileAleksey Kladov2019-05-311-43/+27
|
* simplifyAleksey Kladov2019-05-311-3/+3
|
* introduce constantAleksey Kladov2019-05-311-7/+13
|
* minorAleksey Kladov2019-05-311-1/+1
|
* optimization: cancel backlog in onEnterAleksey Kladov2019-05-291-3/+12
|
* add latest requests to status pageAleksey Kladov2019-05-291-10/+28
|
* log the actual time of requestsAleksey Kladov2019-05-291-16/+31
|
* trigger garbage collection *after* requests, not beforeAleksey Kladov2019-05-291-2/+5
|
* more perf loggingAleksey Kladov2019-05-291-3/+8
|
* Basic resolution for ADTkjeremy2019-04-231-0/+1
|
* switch to official extend selection APIAleksey Kladov2019-04-211-0/+1
|
* Adds support for multiple editor workspaces on initializationRoberto Vidal2019-04-141-14/+17
| | | | This is a quick, partial fix for #1104
* PR issuse resolvedSergey Parilin2019-04-021-4/+3
|
* when loading workspace, say how many packages were loadedAleksey Kladov2019-03-071-7/+7
| | | | | this should help to debug configuration issues, when you see `0 packages loaded` or something like that.
* Add showWorkspaceLoadedNotification to vscode clientVille Penttinen2019-03-061-5/+8
| | | | | | | | | This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent.
* Rename feedback to show_messageVille Penttinen2019-03-051-3/+3
|
* Send an actual ShowMessage instead of InternalFeedback in feedback()Ville Penttinen2019-03-051-16/+21
| | | | | | | This now allows us to send a notification that can be shown in the UI when the workspace has been loaded. Additionally this removes the need for internal_mode flag.
* show message in client's UI if workspace fails to loadAleksey Kladov2019-03-051-7/+12
|
* Remove RawResponse::empty()Ville Penttinen2019-02-271-2/+5
|
* Work around for issue in vscode reporting a failure in requestVille Penttinen2019-02-271-5/+11
| | | | | | vscode would report "A request has failed" when it got "Content modified" message and this would cause a pop-up to appear. This works around the issue by returning an "empty" response that vscode can ignore.
* automatically wait for worker threadsAleksey Kladov2019-02-141-14/+12
| | | | closes #817
* reformat the worldAleksey Kladov2019-02-081-42/+13
|
* Implement lens for impls and support resolving lenses.Jeremy Kolb2019-02-041-0/+1
|
* Go to Implementation for structs and enumsJeremy Kolb2019-01-301-0/+1
|
* automatically collect garbageAleksey Kladov2019-01-271-1/+2
|
* add gc requestAleksey Kladov2019-01-251-9/+18
|
* ad status commandAleksey Kladov2019-01-221-0/+1
|
* rename modgfreezy2019-01-191-4/+1
|
* :arrow_up: update rustAleksey Kladov2019-01-191-1/+0
|
* switch to lsp-typesAleksey Kladov2019-01-141-1/+1
|
* Merge #500bors[bot]2019-01-121-0/+1
|\ | | | | | | | | | | | | | | | | | | | | 500: Code lens support for running tests r=matklad a=kjeremy Supports running individual and mod tests. I feel like this kind of abuses the `Runnables` infrastructure but it works. Maybe later on down the line we should introduce a struct that is really just a tuple of binary, arguments, and environment and pass that back to the client instead. `run_single.ts` is just a paired down version of `runnables.ts` and there is duplication because I think run_single will probably change independent of runnables. Co-authored-by: Jeremy A. Kolb <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Code lens support for running testsJeremy A. Kolb2019-01-111-0/+1
| |
* | warn louder on mising sysrootAleksey Kladov2019-01-111-1/+1
|/
* prioritize event handing over indexingAleksey Kladov2019-01-111-4/+15
| | | | | | If we index gazillion libraries simultaneously, we fill the threadpool and so the main loop fails to turn, although there isn't really any significant blocking inside the loop itself.
* Fix typos in ARCHITECTURE.md and a number of cratesMarcus Klaas de Vries2019-01-091-1/+1
| | | | specifically: gen_lsp_server, ra_arena, ra_cli, ra_db, ra_hir
* fix usages after renameAleksey Kladov2019-01-081-1/+1
|
* refactorSimon Vandel Sillesen2019-01-061-9/+5
|
* extract area to a crateAleksey Kladov2019-01-041-2/+2
|
* Merge #385bors[bot]2018-12-311-0/+1
|\ | | | | | | | | | | | | | | 385: Implement DocumentHighlight r=matklad a=DJMcNab Fixes #80. Co-authored-by: DJMcNab <[email protected]>
| * Implement DocumentHighlightDJMcNab2018-12-311-0/+1
| |
* | remove backtraces from CancelledAleksey Kladov2018-12-301-1/+1
|/ | | | | Hopefully we won't need them for debugging. If we do need them, it should be easy to add back.
* :arrow_up: crossbeamAleksey Kladov2018-12-301-22/+26
| | | | closes #189
* Add support for formatting entire document with rustfmtAleksander Vognild Burkow2018-12-291-0/+1
| | | | | | Attempting to format a document when rustfmt isn't installed will result in an error being returned to the frontend. An alternative implementation would be returning zero replacements.
* add cancelation module & cancelation backtracesAleksey Kladov2018-12-271-1/+1
|
* Merge #326bors[bot]2018-12-241-2/+2
|\ | | | | | | | | | | | | | | 326: resolved #324: remove unnecessary braces in use statement. r=matklad a=gfreezy Add inspection for unnecessary braces in use statement Co-authored-by: gfreezy <[email protected]>
| * remove option from Diagnosticgfreezy2018-12-241-2/+2
| |
* | Merge #302bors[bot]2018-12-241-4/+4
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | 302: WIP: Support tracing lsp requests. r=DJMcNab a=DJMcNab EDIT: We need to work out a better way to handle settings before this can be merged. Help wanted TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway. (Continuation of #84 [#99 only disabled using it, not making sure we don't send it]). These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/ Co-authored-by: DJMcNab <[email protected]>
| * Undo the previous mistaken change and make publish_decorations optionalDJMcNab2018-12-211-4/+4
| | | | | | | | | | | | | | | | See https://github.com/Microsoft/language-server-protocol/issues/567 for motivations to not require `InitializationOptions` TODO: Check if there are any other protocol extensions which should be disabled if not implemented on the client
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-11 06:02:44 +0100