Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | less noisy status | Aleksey Kladov | 2019-05-29 | 1 | -1/+1 |
| | |||||
* | optimization: cancel backlog in onEnter | Aleksey Kladov | 2019-05-29 | 2 | -3/+16 |
| | |||||
* | add latest requests to status page | Aleksey Kladov | 2019-05-29 | 3 | -12/+67 |
| | |||||
* | log the actual time of requests | Aleksey Kladov | 2019-05-29 | 1 | -16/+31 |
| | |||||
* | trigger garbage collection *after* requests, not before | Aleksey Kladov | 2019-05-29 | 1 | -2/+5 |
| | |||||
* | more perf logging | Aleksey Kladov | 2019-05-29 | 1 | -3/+8 |
| | |||||
* | rename stray id field | Pascal Hertleif | 2019-05-27 | 2 | -2/+2 |
| | |||||
* | make it build again | Pascal Hertleif | 2019-05-27 | 1 | -1/+1 |
| | |||||
* | Semantic highlighting spike | Pascal Hertleif | 2019-05-27 | 2 | -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 requests | Aleksey Kladov | 2019-05-27 | 1 | -0/+5 |
| | |||||
* | Added local macro goto | Lenard Pratt | 2019-05-04 | 1 | -0/+1 |
| | |||||
* | Basic resolution for ADT | kjeremy | 2019-04-23 | 3 | -2/+23 |
| | |||||
* | switch to official extend selection API | Aleksey Kladov | 2019-04-21 | 4 | -2/+71 |
| | |||||
* | add a couple of profiling points | Aleksey Kladov | 2019-04-14 | 1 | -0/+3 |
| | |||||
* | filter by time | Aleksey Kladov | 2019-04-14 | 1 | -21/+4 |
| | |||||
* | cleanup syntax | Aleksey Kladov | 2019-04-14 | 1 | -8/+20 |
| | |||||
* | switch to modern paths | Aleksey Kladov | 2019-04-14 | 1 | -5/+5 |
| | |||||
* | Sends cwd info for runnables and code lenses | Roberto Vidal | 2019-04-14 | 3 | -1/+12 |
| | |||||
* | Adds support for multiple editor workspaces on initialization | Roberto Vidal | 2019-04-14 | 3 | -24/+40 |
| | | | | This is a quick, partial fix for #1104 | ||||
* | Refactor CallInfo function signatures to new FunctionSignature type | Ville Penttinen | 2019-04-09 | 2 | -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 exists | Edwin Cheng | 2019-04-07 | 1 | -13/+6 |
| | |||||
* | fix formatting | Edwin Cheng | 2019-04-07 | 1 | -1/+2 |
| | |||||
* | Add warning when open file outside workspace | Edwin Cheng | 2019-04-06 | 1 | -5/+15 |
| | |||||
* | PR issuse resolved | Sergey Parilin | 2019-04-02 | 2 | -4/+13 |
| | |||||
* | Move actual include logic to ProjectRoot | Ville Penttinen | 2019-03-21 | 1 | -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 roots | Ville Penttinen | 2019-03-20 | 3 | -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 Filtering | Ville Penttinen | 2019-03-18 | 1 | -2/+28 |
| | | | | | Currently this matches the previous filtering, meaning all roots are filtered using the same rules. | ||||
* | LSP: Support EnumMember and Field | kjeremy | 2019-03-11 | 1 | -0/+2 |
| | |||||
* | Don't default publishDecorations to true on the server | Florian Diebold | 2019-03-09 | 1 | -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. | ||||
* | when loading workspace, say how many packages were loaded | Aleksey Kladov | 2019-03-07 | 1 | -7/+7 |
| | | | | | this should help to debug configuration issues, when you see `0 packages loaded` or something like that. | ||||
* | Rename and change `add_roots` to return a `Vec`. | David Wood | 2019-03-07 | 1 | -1/+1 |
| | |||||
* | Initial implementation of project-lock.json. | David Wood | 2019-03-07 | 2 | -16/+13 |
| | | | | | 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 client | Ville Penttinen | 2019-03-06 | 4 | -20/+55 |
| | | | | | | | | | 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_message | Ville Penttinen | 2019-03-05 | 1 | -3/+3 |
| | |||||
* | Remove InternalFeedback | Ville Penttinen | 2019-03-05 | 1 | -7/+0 |
| | |||||
* | Send an actual ShowMessage instead of InternalFeedback in feedback() | Ville Penttinen | 2019-03-05 | 2 | -17/+22 |
| | | | | | | | 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 load | Aleksey Kladov | 2019-03-05 | 2 | -8/+14 |
| | |||||
* | Add optional range parameter to SyntaxTreeParams | Ville Penttinen | 2019-03-03 | 2 | -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. | ||||
* | Merge #901 | bors[bot] | 2019-02-27 | 1 | -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 hovering | Ville Penttinen | 2019-02-26 | 1 | -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 Penttinen | 2019-02-27 | 1 | -2/+5 |
| | | |||||
* | | Work around for issue in vscode reporting a failure in request | Ville Penttinen | 2019-02-27 | 1 | -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 well | Aleksey Kladov | 2019-02-25 | 1 | -1/+1 |
| | |||||
* | Assign IDs to assists | Aleksey Kladov | 2019-02-24 | 1 | -9/+39 |
| | |||||
* | Update lsp-types and backtrace | kjeremy | 2019-02-21 | 1 | -1/+1 |
| | |||||
* | Don't use additional_text_edits API internally | Aleksey Kladov | 2019-02-18 | 1 | -6/+26 |
| | |||||
* | Refactor find_all_refs to return ReferenceSearchResult | Ville Penttinen | 2019-02-17 | 2 | -11/+29 |
| | |||||
* | automatically wait for worker threads | Aleksey Kladov | 2019-02-14 | 2 | -17/+15 |
| | | | | closes #817 | ||||
* | Add support for container_name in workspace/symbol query | Ville Penttinen | 2019-02-12 | 1 | -1/+1 |
| | |||||
* | Implement BatchDatabase construction | Florian Diebold | 2019-02-10 | 1 | -3/+1 |
| |