aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/main.ts
Commit message (Collapse)AuthorAgeFilesLines
* Item up and down moversivan7702021-03-181-0/+2
|
* Merge #7799bors[bot]2021-03-131-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7799: Related tests r=matklad a=vsrs ![tests](https://user-images.githubusercontent.com/62505555/109397453-a9013680-7947-11eb-8b11-ac03079f7645.gif) This adds an ability to look for tests for the item under the cursor: function, constant, data type, etc The LSP part is bound to change. But the feature itself already works and I'm looking for a feedback :) Co-authored-by: vsrs <[email protected]>
| * Add LSP request and VSCode commandvsrs2021-02-271-0/+1
| |
* | Make extension respect http proxy settingsKam Y. Tse2021-03-071-2/+4
|/
* Try to detect musl distros in the Code extensionLaurențiu Nicola2021-02-201-2/+12
|
* fix: tolerate spaces in nix binary patchingYaroslav Bolyukin2021-02-131-3/+3
| | | | | | | | | | If path to original file contains space (I.e on code insiders, where default data directory is ~/Code - Insiders/), then there is syntax error evaluating src arg. Instead pass path as str, and coerce to path back in nix expression Signed-off-by: Yaroslav Bolyukin <[email protected]>
* Merge #7625bors[bot]2021-02-101-0/+1
|\ | | | | | | | | | | | | | | | | 7625: Add **Copy Run Command Line** command for vscode r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Add **Copy Run Command Line** command for vscodeAleksey Kladov2021-02-101-0/+1
| | | | | | | | | | This is useful when you want to, e.g., run a specific test in a terminal with `--release`.
* | use await insteadSahandevs2021-02-091-9/+6
| |
* | formatSahandevs2021-02-071-5/+5
| |
* | handle Thenable type rejectsSahandevs2021-02-071-5/+9
|/
* Simplify file download codeLaurențiu Nicola2021-01-251-2/+0
|
* Download aarch64-unknown-linux-gnu from GitHubLaurențiu Nicola2021-01-171-0/+1
|
* Fix server path comparisonLaurențiu Nicola2021-01-141-1/+1
|
* Don't update the server if managed by the userLaurențiu Nicola2021-01-071-1/+6
|
* Allow download of aarch64-pc-windows-msvc binariesLaurențiu Nicola2021-01-041-10/+9
|
* Initial implementation of view-hir commandPhil Ellison2020-12-281-0/+1
|
* 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
* | 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
|/
* 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
|
* add open Cargo.toml actionAnatol Liu2020-11-131-0/+1
|
* WIP: Command to open docs under cursorZac Pullar-Strecker2020-10-081-0/+1
|
* Move unlink on download into download functionMatthias Einwag2020-09-231-11/+3
| | | | | Since this is required by all callsites its easier to have it in the function itself.
* Remane functionMatthias Einwag2020-09-231-5/+5
|
* Use closure in trailing position and strongly type header mapMatthias Einwag2020-09-231-17/+20
|
* Apply suggestions from code reviewMatthias Einwag2020-09-231-1/+1
| | | Co-authored-by: Veetaha <[email protected]>
* Remove stray newlineMatthias Einwag2020-09-231-1/+0
|
* Fix clearing the tokenMatthias Einwag2020-09-231-3/+8
| | | | | | | The previous version would have interpreted an empty token as an abort of the dialog and would have not properly cleared the token. This is now fixed by checking for `undefined` for a an abort and by setting the token to `undefined` in order to clear it.
* Add a command for updating the Github API tokenMatthias Einwag2020-09-231-0/+4
|
* Use retry dialog also for downloadsMatthias Einwag2020-09-231-20/+30
| | | | | | Since the change already implements a retry dialog for network operations, let's also use it for allowing to retry the actual file.
* Fix tslintMatthias Einwag2020-09-231-2/+2
|
* Allow to use a Github Auth token for fetching releasesMatthias Einwag2020-09-231-2/+53
| | | | | | | | | | | | | | | | | | | This change allows to use a authorization token provided by Github in order to fetch metadata for a RA release. Using an authorization token prevents to get rate-limited in environments where lots of RA users use a shared client IP (e.g. behind a company NAT). The auth token is stored in `ExtensionContext.globalState`. As far as I could observe through testing with a local WSL2 environment that state is synced between an extension installed locally and a remote version. The change provides no explicit command to query for an auth token. However in case a download fails it will provide a retry option as well as an option to enter the auth token. This should be more discoverable for most users. Closes #3688
* Gzip artifactsVeetaha2020-07-071-8/+9
| | | | | | | | | | Co-authored-by: bjorn3 <[email protected]> Override miniz_oxide to build it with optimizations Building this crate with optimizations decreases the gzipping part of `cargo xtask dist` from `30-40s` down to `3s`, the overhead for `rustc` to apply optimizations is miserable on this background
* Add a command to compute memory usage statisticsJonas Schievink2020-07-071-0/+1
|
* Consider EPERM error as other vscode processes using rust-analyzerVeetaha2020-07-071-1/+1
|
* Revert "Dispose logger on extension deactivation"Veetaha2020-07-051-2/+0
| | | | | This reverts commit 13872543e074adc153b440660beda441fd562f53. That commit was wrong because we use-after-free the logger
* Dispose logger on extension deactivationVeetaha2020-07-051-0/+2
|
* Improve client logging (use output channel and more log levels)Veetaha2020-07-051-3/+3
|
*---. Merge #5089 #5161 #5184 #5185 #5186bors[bot]2020-07-021-7/+19
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5089: Disable auto-complete on comments r=matklad a=BGluth Resolves #4907 by disabling any auto-completion on comments. As flodiebold [pointed out](https://github.com/rust-analyzer/rust-analyzer/issues/4907#issuecomment-648439979), in the future we may want to support some form of auto-completion within doc comments, but for now it was suggested to just disable auto-completion on them entirely. The implementation involves adding a new field `is_comment` to `CompletionContext` and checking if the immediate token we auto-completed on is a comment. I couldn't see a case where we need to check any of the ancestors, but let me know if this is not sufficient. I also wasn't sure if it was necessary to add a new field to this struct, but I decided it's probably the best option if we want to potentially do auto-completion on doc comments in the future. Finally, the three tests I added should I think ideally not filter results by `CompletionKind::Keyword`, but if I want to get unfiltered results, I need access to a non-public function [get_all_completion_items](https://github.com/rust-analyzer/rust-analyzer/blob/9a4d02faf9c47f401b8756c3f7fcab2198f5f9cd/crates/ra_ide/src/completion/test_utils.rs#L32-L39) which I don't know if I should make public just for this. 5161: SSR: Add initial support for placeholder constraints r=matklad a=davidlattimore 5184: Always install required nightly extension if current one is not nightly r=matklad a=Veetaha This is weird, but having switched back to stable by uninstalling the extension appears that vscode doesn't destroy the `PersistentState` and thus changing to `nightly` channel doesn't work because the last check for nightly extension was less than 1 hour ago. The simple solution is to skip this check if we know that the current extension version is not nightly. 5185: Force showing extension activation error pop-up notification r=matklad a=Veetaha Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5091 5186: fix: correct pd/ppd/tfn/tmod completion doc r=matklad a=fannheyward https://github.com/rust-analyzer/rust-analyzer/blob/a33eefa3b26000b3018e6bb873f18dbe15ab4ab7/crates/ra_ide/src/completion/complete_snippet.rs#L23-L24 Co-authored-by: BGluth <[email protected]> Co-authored-by: David Lattimore <[email protected]> Co-authored-by: Veetaha <[email protected]> Co-authored-by: Heyward Fann <[email protected]>
| | | * Force showing extension activation error pop-up notificationVeetaha2020-07-021-3/+11
| | |/ | |/|
| | * Always install required nightly extension if current one is not nightlyVeetaha2020-07-021-4/+8
| |/
* / Add reload workspace commandAleksey Kladov2020-07-011-1/+1
|/
* Merge #5017bors[bot]2020-06-261-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | 5017: Add custom cargo runners support. r=matklad a=vsrs This PR adds an option to delegate actual cargo commands building to another extension. For example, to use a different manager like [cross](https://github.com/rust-embedded/cross). https://github.com/vsrs/cross-rust-analyzer is an example of such extension. I'll publish it after the rust-analyzer release with this functionality. Fixes https://github.com/rust-analyzer/rust-analyzer/issues/4902 Co-authored-by: vsrs <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 05:47:30 +0100