Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add `rust-analyzer.gotoLocation` command | vsrs | 2020-06-18 | 1 | -0/+1 |
| | |||||
* | Preliminary implementation of lazy CodeAssits | Mikhail Rakhmanov | 2020-06-02 | 1 | -0/+1 |
| | |||||
* | Add `inRustProject` when-clause for commands. | vsrs | 2020-05-27 | 1 | -0/+6 |
| | |||||
* | Flatten commands.ts | Aleksey Kladov | 2020-05-25 | 1 | -1/+0 |
| | |||||
* | Introduce `toggle inlay hints` vscode command | veetaha | 2020-05-25 | 1 | -0/+1 |
| | | | | | | | | Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599 | ||||
* | Merge #4555 #4575 | bors[bot] | 2020-05-23 | 1 | -1/+48 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4555: VSCode: added patchelf after download for NixOS support r=matklad a=cab404 This adds Nix support, and fixes #4542 4575: Use Chalk's built-in representations for fn items and pointers r=matklad a=flodiebold The `TypeName::FnDef` was just added; the function pointer variant has existed for a while, I just forgot about it because it's special (because fn pointers can be higher-ranked over lifetimes). We *could* also make `FnPtr` a separate `Ty` variant instead of a `TypeCtor` variant, which would make the conversion code a bit less special-casey, but it doesn't seem worth doing right now. Co-authored-by: Vladimir Serov <[email protected]> Co-authored-by: Cabia Rangris <[email protected]> Co-authored-by: Florian Diebold <[email protected]> | ||||
| * | Merge branch 'nix-patchelf' of github.com:cab404/rust-analyzer into nix-patchelf | Vladimir Serov | 2020-05-21 | 1 | -1/+1 |
| |\ | |||||
| | * | Update editors/code/src/main.ts | Cabia Rangris | 2020-05-21 | 1 | -1/+1 |
| | | | | | | | | | Co-authored-by: Jeremy Kolb <[email protected]> | ||||
| * | | editors/vscode: forgotten await in os check | Vladimir Serov | 2020-05-21 | 1 | -1/+1 |
| | | | |||||
| * | | editors/vscode: patchelf-ing without intermediate files | Vladimir Serov | 2020-05-21 | 1 | -5/+5 |
| |/ | |||||
| * | editor/vscode: lint | Vladimir Serov | 2020-05-21 | 1 | -21/+21 |
| | | |||||
| * | editors/vscode: removing original file after patching | Vladimir Serov | 2020-05-21 | 1 | -1/+1 |
| | | |||||
| * | editors/vscode: added patchelf after download | Vladimir Serov | 2020-05-21 | 1 | -1/+48 |
| | | |||||
* | | CodeAction groups | Aleksey Kladov | 2020-05-22 | 1 | -1/+1 |
| | | |||||
* | | Transition OnEnter to WorkspaceSnippetEdit | Aleksey Kladov | 2020-05-21 | 1 | -1/+1 |
|/ | | | | | | | | This also changes our handiling of snippet edits on the client side. `editor.insertSnippet` unfortunately forces indentation, which we really don't want to have to deal with. So, let's just implement our manual hacky way of dealing with a simple subset of snippets we actually use in rust-analyzer | ||||
* | Implement client-side of SnippetTextEdit | Aleksey Kladov | 2020-05-19 | 1 | -0/+1 |
| | |||||
* | "rust-analyzer.newDebugConfig" command | vsrs | 2020-05-11 | 1 | -0/+1 |
| | |||||
* | "rust-analyzer.debug" command | vsrs | 2020-05-11 | 1 | -0/+1 |
| | |||||
* | Fix cargo not found on macos bug at vscode extension side | veetaha | 2020-05-06 | 1 | -6/+2 |
| | |||||
* | vscode: log server binary path | veetaha | 2020-04-04 | 1 | -0/+2 |
| | |||||
* | Remove old syntax highlighting | Aleksey Kladov | 2020-04-02 | 1 | -4/+0 |
| | |||||
* | Pass string instread of WorkspaceFolder | Tim | 2020-03-31 | 1 | -1/+1 |
| | |||||
* | Remove unnecessary null check | Tim | 2020-03-31 | 1 | -3/+1 |
| | |||||
* | Throw error if no folder is opened | Tim | 2020-03-31 | 1 | -1/+6 |
| | |||||
* | Add basic task support | Tim | 2020-03-30 | 1 | -1/+8 |
| | | | | This adds basic support for running `cargo build`, `cargo run`, etc. | ||||
* | Code review fixes | Kirill Bulatov | 2020-03-30 | 1 | -1/+1 |
| | | | | Co-Authored-By: Veetaha <[email protected]> | ||||
* | Client side draft | Kirill Bulatov | 2020-03-30 | 1 | -0/+6 |
| | |||||
* | vscode: small post-refactor | veetaha | 2020-03-26 | 1 | -3/+1 |
| | |||||
* | vscode: fix memory leak on server restart | veetaha | 2020-03-26 | 1 | -15/+13 |
| | | | | The memory leak was because on the server restrart the array of extensionContext.substiptions was not cleared | ||||
* | vscode: fix local devel | veetaha | 2020-03-26 | 1 | -4/+6 |
| | | | | The value of releaseTag is not undefined, but null in actual package.json | ||||
* | Use the right arch name for x86 (32 bit) | Aleksey Kladov | 2020-03-25 | 1 | -1/+1 |
| | |||||
* | Don't try to enable proposed API's on stable | Aleksey Kladov | 2020-03-24 | 1 | -7/+7 |
| | |||||
* | Make from-source install use cargo installed binary by default | Aleksey Kladov | 2020-03-20 | 1 | -0/+2 |
| | |||||
* | Simplify extension tag sniffing | Aleksey Kladov | 2020-03-19 | 1 | -2/+2 |
| | |||||
* | Rewrite auto-update | Aleksey Kladov | 2020-03-19 | 1 | -20/+138 |
| | | | | | | | | | | | | | | Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server). | ||||
* | Separate persistent mutable state from config | Aleksey Kladov | 2020-03-16 | 1 | -4/+6 |
| | | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent. | ||||
* | Merge #3534 | bors[bot] | 2020-03-16 | 1 | -1/+8 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3534: Feature: vscode impl nightlies download and installation r=Veetaha a=Veetaha I need to test things more, but the core shape of the code is quite well-formed. The main problem is that we save the release date only for nightlies and there are no means to get the release date of the stable extension (i.e. for this we would need to consult the github releases via a network request, or we would need to somehow save this info into package.json or any other file accessible from the extension code during the deployment step, but this will be very hard I guess). So there is an invariant that the users can install nightly only from our extension and they can't do it manually, because when installing the nightly `.vsix` we actually save its release date to `globalState` Closes: #3402 TODO: - [x] More manual tests and documentation cc @matklad @lnicola Co-authored-by: Veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]> | ||||
| * | vscode-postrefactor: unhandled promise rejections shall not pass 2 | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | | |||||
| * | vscode-postrefactor: unhandled promise rejections shall not pass | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | | |||||
| * | vscode: amend server installation logic to account for nightlies | Veetaha | 2020-03-14 | 1 | -1/+8 |
| | | |||||
* | | feat: add debug code lens | Hannes De Valkeneer | 2020-03-11 | 1 | -0/+1 |
|/ | | | | Refs #3539 | ||||
* | Config to switch to semantic tokens | Aleksey Kladov | 2020-02-26 | 1 | -1/+3 |
| | |||||
* | Don't break onEnter if rust-analyzer fails to start | Aleksey Kladov | 2020-02-24 | 1 | -0/+23 |
| | | | | closes #3253 | ||||
* | Extract client-side logging | Aleksey Kladov | 2020-02-22 | 1 | -1/+2 |
| | |||||
* | Improve server version info | Edwin Cheng | 2020-02-21 | 1 | -0/+1 |
| | |||||
* | vscode: press ; to respect semicolons | Veetaha | 2020-02-17 | 1 | -6/+6 |
| | |||||
* | Remove two stage constuction | Aleksey Kladov | 2020-02-17 | 1 | -7/+4 |
| | |||||
* | Fix link to the manual | Aleksey Kladov | 2020-02-17 | 1 | -1/+1 |
| | |||||
* | Push IO and error handling up | Aleksey Kladov | 2020-02-17 | 1 | -1/+10 |
| | |||||
* | Simplify startup | Aleksey Kladov | 2020-02-17 | 1 | -10/+11 |
| |