aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server
Commit message (Collapse)AuthorAgeFilesLines
...
* | Semantic highlighting spikePascal Hertleif2019-05-272-1/+6
|/ | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* add profile calls to real-time requestsAleksey Kladov2019-05-271-0/+5
|
* Added local macro gotoLenard Pratt2019-05-041-0/+1
|
* Basic resolution for ADTkjeremy2019-04-233-2/+23
|
* :arrow_up: lspAleksey Kladov2019-04-211-1/+1
|
* switch to official extend selection APIAleksey Kladov2019-04-215-3/+72
|
* cleanup cancellationAleksey Kladov2019-04-171-10/+5
| | | | | Now that we explicitelly exit the reading loop on exit notification, we can assume that the sender is always alive
* add a couple of profiling pointsAleksey Kladov2019-04-141-0/+3
|
* filter by timeAleksey Kladov2019-04-141-21/+4
|
* cleanup syntaxAleksey Kladov2019-04-141-8/+20
|
* switch to modern pathsAleksey Kladov2019-04-141-5/+5
|
* Modifies runnables test to use multi-workspace rootRoberto Vidal2019-04-142-29/+68
|
* Sends cwd info for runnables and code lensesRoberto Vidal2019-04-145-3/+22
|
* Adds support for multiple editor workspaces on initializationRoberto Vidal2019-04-144-25/+41
| | | | This is a quick, partial fix for #1104
* Refactor CallInfo function signatures to new FunctionSignature typeVille Penttinen2019-04-092-18/+27
| | | | | This is used by CallInfo to create a pretty printed function signature that can be used with completions and other places as well.
* Remove checking file existsEdwin Cheng2019-04-071-13/+6
|
* fix formattingEdwin Cheng2019-04-071-1/+2
|
* Add warning when open file outside workspaceEdwin Cheng2019-04-061-5/+15
|
* PR issuse resolvedSergey Parilin2019-04-023-4/+14
|
* Move actual include logic to ProjectRootVille Penttinen2019-03-211-25/+20
| | | | | This way the two IncludeRustFiles implementations can simply call the ProjectRoots' methods, so that the include logic is in one place.
* Improve filtering of file rootsVille Penttinen2019-03-203-29/+65
| | | | | | | | | `ProjectWorkspace::to_roots` now returns a new `ProjectRoot` which contains information regarding whether or not the given path is part of the current workspace or an external dependency. This information can then be used in `ra_batch` and `ra_lsp_server` to implement more advanced filtering. This allows us to filter some unnecessary folders from external dependencies such as tests, examples and benches.
* Upgrade ra_vfs to use new FilteringVille Penttinen2019-03-182-3/+29
| | | | | Currently this matches the previous filtering, meaning all roots are filtered using the same rules.
* LSP: Support EnumMember and Fieldkjeremy2019-03-111-0/+2
|
* Don't default publishDecorations to true on the serverFlorian Diebold2019-03-091-39/+61
| | | | | | | If the client doesn't specify this explicitly, that very likely means it doesn't know about it and so we shouldn't send decorations. In particular, the recent change to this default caused decorations to be sent to emacs, resulting in a lot of warning spam.
* Merge #948bors[bot]2019-03-071-6/+11
|\ | | | | | | | | | | | | | | | | | | | | | | 948: Fix test_missing_module_code_action_in_json_project on Windows r=matklad a=vipentti The test would fail on Windows due to the paths not being properly escaped for JSON. In addition adds extra braces around the fn main to actually introduce braces in the file. Co-authored-by: Ville Penttinen <[email protected]>
| * Fix test_missing_module_code_action_in_json_project on WindowsVille Penttinen2019-03-071-6/+11
| | | | | | | | | | | | | | | | The test would fail on Windows due to the paths not being properly escaped for JSON. In addition adds extra braces around the fn main to actually introduce braces in the file.
* | Specify derive feature for serdepcpthm2019-03-071-1/+1
|/
* when loading workspace, say how many packages were loadedAleksey Kladov2019-03-073-22/+21
| | | | | this should help to debug configuration issues, when you see `0 packages loaded` or something like that.
* Remove rust-project.json test w/ dependencies.David Wood2019-03-071-43/+0
|
* Add test demonstrating logic for handling deps.David Wood2019-03-071-1/+44
|
* Rename and change `add_roots` to return a `Vec`.David Wood2019-03-071-1/+1
|
* Initial implementation of project-lock.json.David Wood2019-03-074-18/+82
| | | | | This commit adds a initial implementation of project-lock.json, a build system agnostic method of specifying the crate graph and roots.
* Add showWorkspaceLoadedNotification to vscode clientVille Penttinen2019-03-065-21/+63
| | | | | | | | | 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-053-13/+13
|
* Remove InternalFeedbackVille Penttinen2019-03-051-7/+0
|
* Send an actual ShowMessage instead of InternalFeedback in feedback()Ville Penttinen2019-03-053-20/+27
| | | | | | | 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.
* Updateskjeremy2019-03-051-1/+1
|
* show message in client's UI if workspace fails to loadAleksey Kladov2019-03-052-8/+14
|
* Add optional range parameter to SyntaxTreeParamsVille Penttinen2019-03-032-1/+4
| | | | | When range is provided, instead of showing the syntax for the whole file, we'll show the syntax tree for the given range.
* Fix the buildkjeremy2019-02-271-1/+3
|
* Merge #901bors[bot]2019-02-271-1/+1
|\ | | | | | | | | | | | | | | | | | | 901: Add basic support for showing fn signature when hovering r=matklad a=vipentti This adds basic support for displaying function signature when hovering over a usage of a function. Additionally refactored `hover` to return `HoverResult` to ease with testing and in general to be more robust. Co-authored-by: Ville Penttinen <[email protected]>
| * Add new type HoverResult to contain the results of hoveringVille Penttinen2019-02-261-1/+1
| | | | | | | | | | This makes testing hovers easier as well as allows us to do more things with the results if needed.
* | 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.
* rename type to type_alias in the AST as wellAleksey Kladov2019-02-251-1/+1
|
* Assign IDs to assistsAleksey Kladov2019-02-242-13/+46
|
* Update lsp-types and backtracekjeremy2019-02-212-2/+2
|
* switch to crates.io vfsAleksey Kladov2019-02-181-1/+1
|
* drop unused depsAleksey Kladov2019-02-181-3/+0
|
* Don't use additional_text_edits API internallyAleksey Kladov2019-02-181-6/+26
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 21:30:40 +0000