aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
* Remove deprecation support in configLukas Wirth2021-06-211-6/+0
|
* Add configuration deprecationLukas Wirth2021-06-141-0/+6
|
* Make documentation on hover configurableLukas Wirth2021-06-141-5/+10
|
* Merge #8951bors[bot]2021-06-144-47/+38
|\ | | | | | | | | | | | | | | 8951: internal: migrate to vscode.FileSystem API r=matklad a=wxb1ank I encountered an error where `bootstrap()` attempts to create a directory with the path `C:\C:\...`. I couldn't find this reported anywhere else. Using the `vscode.FileSystem` API instead of the `fs` one works here. I assume the latter automatically prepends `C:\` to paths whereas the former does not. I don't know if this suggests `vscode.FileSystem` should be used in more places for consistency. Co-authored-by: wxb1ank <[email protected]>
| * Lint toolchain.tswxb1ank2021-06-021-1/+1
| |
| * migrate from `fs` to `vscode.FileSystem` APIwxb1ank2021-06-023-44/+35
| |
| * internal: use vscode.FileSystem API in main.tswxb1ank2021-06-022-5/+5
| |
* | Revert "Merge #9177"Aleksey Kladov2021-06-081-342/+335
| | | | | | | | | | | | | | This reverts commit f1818cb7ba2808cba3fd9bf8f199c382060a1f19, reversing changes made to 6c9362d61b895c11b1d0cf6837ada9f2a0a30eaf. This broke things
* | Merge #9177bors[bot]2021-06-081-335/+342
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 9177: :arrow_up: npm packages r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | :arrow_up: npm packagesAleksey Kladov2021-06-081-335/+342
| | |
* | | fixMilo2021-06-071-1/+1
| | |
* | | fixMilo2021-06-061-1/+1
| | |
* | | when you click status bar icon it now restarts serverMilo2021-06-061-0/+1
|/ /
* | Add function references hover actionLukas Wirth2021-06-042-0/+6
| |
* | Make it opt-inJonas Schievink2021-06-031-0/+5
| |
* | Document that `addCallArgumentSnippets` requires `addCallParenthesisLukas Wirth2021-06-021-1/+1
|/
* Fix opening single filesKirill Bulatov2021-05-311-1/+1
|
* fix: fix shell injection in task spawningAleksey Kladov2021-05-311-6/+6
| | | | closes #9058
* Add config setting for self-on-the-flyLukas Wirth2021-05-311-0/+5
|
* Fix incorrect setting descriptionsLucas Schwiderski2021-05-291-2/+2
| | | | | | | | Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <[email protected]>
* Merge #8995bors[bot]2021-05-264-22/+20
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8995: fix: Create tasks for all workspaces r=matklad a=SomeoneToIgnore Follow-up of https://github.com/rust-analyzer/rust-analyzer/pull/8955#discussion_r637897170 Before: <img width="593" alt="image" src="https://user-images.githubusercontent.com/2690773/119575267-712b5300-bdbf-11eb-833c-f688f7a7dd0f.png"> After: <img width="643" alt="image" src="https://user-images.githubusercontent.com/2690773/119575273-74264380-bdbf-11eb-8283-a78bbcb7346e.png"> This is the first time I've used multiple workspaces feature in VSCode, but so far looks like * opening detached files works * run and debug lens work * Rust Analyzer: Run action works * run task works and now shows tasks for all workspaces * there are no platform-specific changes involved Co-authored-by: Kirill Bulatov <[email protected]>
| * Create tasks for all workspacesKirill Bulatov2021-05-254-22/+20
| |
* | Merge #9001bors[bot]2021-05-261-0/+4
|\ \ | |/ |/| | | | | | | | | | | | | 9001: minor: explicitly set the focus to false r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * minor: explicitly set the focus to falseAleksey Kladov2021-05-261-0/+4
| |
* | Merge #8767bors[bot]2021-05-251-0/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 8767: implement range formatting r=matklad a=euclio Fixes #7580. This PR implements the `textDocument/rangeFormatting` request using `rustfmt`'s `--file-lines` option. Still needs some tests. What I want to know is how I should handle the instability of the `--file-lines` option. It's still unstable in rustfmt, so it's only available on nightly, and needs a special flag to enable. Is there a way for `rust-analyzer` to detect if it's using nightly rustfmt, or for users to opt-in? Co-authored-by: Andy Russell <[email protected]>
| * implement range formattingAndy Russell2021-05-231-0/+5
| |
* | fix: cursor position after item move commandEduardo Canellas2021-05-241-1/+1
| | | | | | | | closes Item movers need some fixes #8492
* | Merge #8955bors[bot]2021-05-243-41/+69
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8955: feature: Support standalone Rust files r=matklad a=SomeoneToIgnore ![standalone](https://user-images.githubusercontent.com/2690773/119277037-0b579380-bc26-11eb-8d77-20d46ab4916a.gif) Closes https://github.com/rust-analyzer/rust-analyzer/issues/6388 Caveats: * I've decided to support multiple detached files in the code (anticipating the scratch files), but I found no way to open multiple files in VSCode at once: running `code *.rs` makes the plugin to register in the `vscode.workspace.textDocuments` only the first file, while code actually displays all files later. Apparently what happens is the same as when you have VSCode open at some workplace already and then run `code some_other_file.rs`: it gets opened in the same workspace of the same VSCode with no server to support it. If there's a way to override it, I'd appreciate the pointer. * No way to toggle inlay hints, since the setting is updated for the workspace (which does not exist for a single file opened) > [2021-05-24 00:22:49.100] [exthost] [error] Error: Unable to write to Workspace Settings because no workspace is opened. Please open a workspace first and try again. * No runners/lens to run or check the code are implemented for this mode. In theory, we can detect `rustc`, run it on a file and run the resulting binary, but not sure if worth doing it at this stage. Otherwise imports, hints, completion and other features work. Co-authored-by: Kirill Bulatov <[email protected]>
| * | Fix ts lint errorsKirill Bulatov2021-05-233-8/+8
| | |
| * | Send detached files info to server via init paramsKirill Bulatov2021-05-233-6/+27
| | |
| * | Start rust-analyzer server for arbitrary rust filesKirill Bulatov2021-05-233-39/+46
| |/
* | fix: can download server binary on windows againAleksey Kladov2021-05-241-1/+1
| | | | | | | | | | | | Closes #8956 See https://github.com/rust-analyzer/rust-analyzer/pull/8951#issuecomment-846716999
* | fix: reveal snippetsAleksey Kladov2021-05-231-0/+3
|/
* More style fixesKirill Bulatov2021-05-232-16/+19
|
* Style fixKirill Bulatov2021-05-232-12/+11
|
* Don't use a deprecated accessorKirill Bulatov2021-05-231-1/+1
|
* Better releaseId namingKirill Bulatov2021-05-232-12/+11
|
* Remove nightly release id from local storage for stable extensionsKirill Bulatov2021-05-232-1/+6
|
* Download nightly extension when configured and run from stable extension versionKirill Bulatov2021-05-231-3/+10
|
* Use `.rs` file ending to get syntax highlightingJonas Schievink2021-05-211-1/+1
|
* Add a "Debug ItemTree" LSP requestJonas Schievink2021-05-214-0/+62
|
* Merge #8873bors[bot]2021-05-201-7/+14
|\ | | | | | | | | | | | | | | | | | | | | | | 8873: Implement import-granularity guessing r=matklad a=Veykril This renames our `MergeBehavior` to `ImportGranularity` as rustfmt has it as the purpose of them are basically the same. `ImportGranularity::Preserve` currently has no specific purpose for us as we don't have an organize imports assist yet, so it currently acts the same as `ImportGranularity::Item`. We now try to guess the import style on a per file basis and fall back to the user granularity setting if the file has no specific style yet or where it is ambiguous. This can be turned off by setting `import.enforceGranularity` to `true`. Closes https://github.com/rust-analyzer/rust-analyzer/issues/8870 Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * Replace ImportGranularity::Guess with guessing boolean flagLukas Tobias Wirth2021-05-191-3/+6
| |
| * Add ImportGranularity::GuessLukas Tobias Wirth2021-05-181-1/+3
| |
| * MergeBehavior -> ImportGranularityLukas Tobias Wirth2021-05-181-8/+10
| |
* | Add new LSP extension for workspace symbol lookupalcroito2021-05-171-0/+26
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* minor: adjust config nameAleksey Kladov2021-05-171-5/+5
|
* Merge #8795bors[bot]2021-05-171-0/+5
|\ | | | | | | | | | | | | | | | | | | 8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
| * Formatting and docsJohn Renner2021-05-101-0/+5
| |
* | Allow viewing the crate graph in a webviewJonas Schievink2021-05-114-0/+16
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-25 14:07:06 +0000