rust-analyzer/editors/code
bors[bot] 200c275c2e
Merge #3534
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 <gerzoh1@gmail.com>
Co-authored-by: Veetaha <veetaha2@gmail.com>
2020-03-16 10:26:31 +00:00
..
src Merge #3534 2020-03-16 10:26:31 +00:00
.eslintrc.js vscode: remove type assertion 2020-02-24 21:23:56 +02:00
.gitignore add rollup bundler for vscode extension 2019-09-23 23:25:16 +02:00
.vscodeignore Actually include readme into .vsix 2020-03-03 18:40:27 +01:00
icon.png Extension icon 2020-01-15 16:07:39 +01:00
package-lock.json vscode: sync package-lock.json version with package.json 2020-03-14 03:20:39 +02:00
package.json vscode: prepare package.json for nightlies 2020-03-14 02:01:46 +02:00
README.md Minimal viable meta 2020-03-02 14:27:26 +01:00
rollup.config.js Disable rollup warning 2020-02-16 05:04:51 +08:00
tsconfig.json vscode: amended config to use binary from globalStoragePath, added ui for downloading 2020-02-08 04:34:11 +02:00

rust-analyzer

Provides support for rust-analyzer: novel LSP server for the Rust programming language.

See https://rust-analyzer.github.io/ for more information.