aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
* update format.ShuiRuTian2021-01-101-8/+9
|
* fix issue.ShuiRuTian2021-01-101-0/+7
|
* beta version for folder renameShuiRuTian2021-01-091-0/+12
|
* Rename extension configAleksey Kladov2021-01-042-2/+4
|
* Allow download of aarch64-pc-windows-msvc binariesLaurențiu Nicola2021-01-041-10/+9
|
* Merge #7068bors[bot]2021-01-034-0/+66
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7068: Add VSCode command to view the hir of a function body r=theotherphil a=theotherphil Will fix https://github.com/rust-analyzer/rust-analyzer/issues/7061. Very rough initial version just to work out where I needed to wire everything up. @matklad would you be happy merging a hir visualiser of some kind? If so, do you have any thoughts on what you'd like it show, and how? I've spent very little time on this thus far, so I'm fine with throwing away the contents of this PR, but I want to avoid taking the time to make this more polished/interactive/useful only to discover that no-one else has any interest in this functionality. ![image](https://user-images.githubusercontent.com/1974256/103236081-bb58f700-493b-11eb-9d12-55ae1b870f8f.png) Co-authored-by: Phil Ellison <[email protected]>
| * Remove some unnecessary code copied from the Syntax Tree commandPhil Ellison2021-01-011-17/+3
| |
| * Initial implementation of view-hir commandPhil Ellison2020-12-284-0/+80
| |
* | Add an option for extra env vars in the Code extensionlf-2020-12-304-3/+21
| |
* | Apply text edits manually in vscode clientLukas Wirth2020-12-291-2/+8
|/
* Merge #7001bors[bot]2020-12-221-6/+8
|\ | | | | | | | | | | | | | | | | | | 7001: Add support for downloading aarch64-apple-darwin binaries r=matklad a=lnicola There's also a slight behavior change here: we no longer download our 64-binaries on 32-bit Darwin and Linux. We still do that on Windows, as I don't know how to detect 32-bit Node on 64 Windows. But some people install the 32-bit Code by mistake, I doubt 32-bit Windows is that popular in the Rust crowd. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Add support for downloading aarch64-apple-darwin binaries, change naming ↵Laurențiu Nicola2020-12-221-6/+8
| | | | | | | | convention
* | Merge #7002bors[bot]2020-12-221-5/+15
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 7002: Extension conflict check detects more combinations r=extremegf a=extremegf This will also detect conflicts with kalitaalexey.vscode-rust and work correctly after RA is integrated with rust-lang.rust extension. Co-authored-by: Przemyslaw Horban <[email protected]> Co-authored-by: P. Horban <[email protected]>
| * | Fix grammar nitP. Horban2020-12-221-1/+1
| | | | | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Extension conflict check detests more combinationsPrzemyslaw Horban2020-12-221-5/+15
| |/
* | Merge #6993bors[bot]2020-12-221-25/+25
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 6993: Clean up descriptions for settings r=matklad a=rherrmann Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, command line arguments, etc. as `code`. Format mentions of UI elements in _italic_. Fix typos, add missing full-stops, add missing default values. Co-authored-by: Rüdiger Herrmann <[email protected]>
| * Clean up descriptions for settingsRüdiger Herrmann2020-12-221-25/+25
| | | | | | | | | | | | | | | | | | | | | | | | Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
* | Merge #6746bors[bot]2020-12-221-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6746: Feature/add assist extract module to file r=matklad a=sasurau4 Fix #6522 ## Screenshot <img src="https://user-images.githubusercontent.com/13580199/102748269-33a44300-43a5-11eb-9e37-f5fcb8e62f73.gif" width=600 /> ## TODO - [x] Remove all TODO comment - [x] Pass the doc test Co-authored-by: Daiki Ihara <[email protected]>
| * | Use workspace applyEdit instead of snippetWorkspaceEditDaiki Ihara2020-12-211-1/+1
| | |
* | | Merge #6984bors[bot]2020-12-223-1146/+0
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | 6984: Remove TextMate grammar r=dustypomerleau a=lnicola Closes #6267 This is now included upstream in VS Code. Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Remove TextMate grammarLaurențiu Nicola2020-12-213-1146/+0
| |/ | | | | | | It's now included upstream in VS Code
* | Don't download x64 binaries on non-Mac arm64Laurențiu Nicola2020-12-211-1/+3
| |
* | Allow code extension to download binary in apple armSon2020-12-211-1/+1
| |
* | Remove outdated FIXMELaurențiu Nicola2020-12-211-3/+2
| |
* | Use /etc/os-release to check for NixOSLaurențiu Nicola2020-12-211-1/+10
|/ | | | | | The motivation in #5641 isn't too strong, but /etc/os-release exists on pretty much every Linux distro, while /etc/nixos sounds like an implementation detail.
* Fixed formattingPrzemyslaw Horban2020-12-181-2/+2
|
* Added a warning if conflicting rust-lang.rust is enabled.Przemyslaw Horban2020-12-181-0/+11
|
* LSP 3.16 - Releasedkjeremy2020-12-172-31/+46
|
* add language-configuration.json to .vscodeignoreBryan Gin-ge Chen2020-12-151-0/+1
|
* add a language configuration for VS CodeDusty Pomerleau2020-12-132-0/+49
|
* Make config.rs a single source of truth for configuration.Aleksey Kladov2020-12-081-320/+304
| | | | | | | | | | | | | | | | | Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
* Merge #6706bors[bot]2020-12-081-2/+5
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6706: Move import text edit calculation into a completion resolve request r=matklad a=SomeoneToIgnore Part of https://github.com/rust-analyzer/rust-analyzer/issues/6612 (presumably fixing it) Part of https://github.com/rust-analyzer/rust-analyzer/issues/6366 (does not cover all possible resolve capabilities we can do) Closes https://github.com/rust-analyzer/rust-analyzer/issues/6594 Further improves imports on completion performance by deferring the computations for import inserts. To use the new mode, you have to have the experimental completions enabled and use the LSP 3.16-compliant client that reports `additionalTextEdits` in its `CompletionItemCapabilityResolveSupport` field in the client capabilities. rust-analyzer VSCode extension does this already hence picks up the changes completely. Performance implications are descrbed in: https://github.com/rust-analyzer/rust-analyzer/issues/6633#issuecomment-737295182 Co-authored-by: Kirill Bulatov <[email protected]>
| * Better config nameKirill Bulatov2020-12-081-3/+6
| |
| * Disable the completion for no corresponding client resolve capabilitiesKirill Bulatov2020-12-071-3/+3
| |
* | Remove workaround & fix fetch$1 is not a functionKafji2020-12-081-4/+1
|/ | | | | | | | | Remove workaround for https://github.com/rollup/plugins/issues/491 because it's fixed in 15.0 https://github.com/rollup/plugins/blob/master/packages/commonjs/CHANGELOG.md#v1500. Also fix fetch$1 is not a function error https://github.com/rust-analyzer/rust-analyzer/issues/6757.
* Update npm packageskjeremy2020-12-072-691/+579
|
* Merge #6496bors[bot]2020-11-261-3/+0
|\ | | | | | | | | | | | | | | | | | | 6496: Use builtin scopes more r=matklad a=georgewfraser VSCode has added more builtin fallback scopes, so we can remove some of our fallback scopes by aligning with their conventions. Note that the macro scope doesn't seem to actually *work* at the moment. I have filed a bug with VSCode: https://github.com/microsoft/vscode/issues/110150 Co-authored-by: George Fraser <[email protected]>
| * Just remove the macro fallbackGeorge Fraser2020-11-251-0/+6
| |
| * Use builtin scopes moreGeorge Fraser2020-11-071-9/+0
| |
* | Gate autoimports begind experimental completions flagKirill Bulatov2020-11-241-0/+5
| |
* | ensure word boundary after `true`Dusty Pomerleau2020-11-211-1/+1
| |
* | Use vscode-languageclient 7.0.0-next.14kjeremy2020-11-173-13/+15
| |
* | Cleanup workspace loading a tiny bitAleksey Kladov2020-11-131-5/+5
| |
* | Merge #6519bors[bot]2020-11-134-0/+37
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6519: Add "Open Cargo.toml" action r=matklad a=p3achyjr ## What is it? This adds an "open cargo.toml" action from the vscode shell, resolves #6462 ## Test Ran ```cargo xtask install --server``` and ```cargo xtask install --client```, then ```Developer: Reload Window```. ![image](https://user-images.githubusercontent.com/8763808/98614382-2a578f00-22ad-11eb-9811-4a72a54ff6fb.png) When clicked: ![image](https://user-images.githubusercontent.com/8763808/98618176-77d7fa00-22b5-11eb-8788-35256542f3a6.png) Co-authored-by: Anatol Liu <[email protected]>
| * | add open Cargo.toml actionAnatol Liu2020-11-134-0/+37
| | |
* | | Revert "Upgrade version of npms lockfile"Aleksey Kladov2020-11-131-2754/+10
| | | | | | | | | | | | | | | | | | | | | This reverts commit 3d559afc11b230d52b13c5540706b85a7eeb3490. VS Code uses nodejs 12 still, so its better to stick to the format it understands.
* | | Upgrade version of npms lockfileAleksey Kladov2020-11-121-10/+2754
| | |
* | | Address review commentsXavier Denis2020-11-122-3378/+15
| | |
* | | Add support for loading rustc private cratesXavier Denis2020-11-112-10/+3381
|/ /
* | Switch to upstream protocol for resolving code actionAleksey Kladov2020-11-103-20/+18
| | | | | | | | | | | | 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.