aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Use closure in trailing position and strongly type header mapMatthias Einwag2020-09-232-18/+21
|
* 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-233-4/+72
| | | | | | | | | | | | | | | | | | | 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
* Fix LSP requests with no argumentsLaurențiu Nicola2020-09-172-6/+6
|
* Fix delimiter in SSR exampleLaurențiu Nicola2020-09-151-1/+1
|
* Move to vscode-languageclient 7.0.0-next.9kjeremy2020-09-024-18/+9
| | | | Stabilizes call hierarchy and semantic tokens features.
*-. Merge #5910 #5912bors[bot]2020-08-292-2/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5910: Fix some typos r=matklad a=SomeoneToIgnore 5912: Remove fixme from inlay_hints.ts r=matklad a=Veetaha I have reevaluated the fixme and it doesn't seem necessary to pass an array of files to the inlay hints request. This will (a) make the request more compilcated (b), make us wait for inlay hints for `all` active editors resolve at once before rendering and (c) doesn't seem required because 99% of the time there is a single active editor in the IDE Co-authored-by: Kirill Bulatov <[email protected]> Co-authored-by: Veetaha <[email protected]>
| | * Remove fixme from inlay_hints.tsVeetaha2020-08-291-1/+0
| |/ |/| | | | | | | | | | | | | | | I have reevaluated the fixme and it doesn't seem necessary to pass an array of files to the inlay hints request. This will (a) make the request more compilcated (b), make us wait for inlay hints for `all` active editors resolve at once before rendering and (c) doesn't seem required because 99% of the time there is a single active editor in the IDE
| * Fix some typosKirill Bulatov2020-08-281-1/+1
|/
* Make inlay hints colors more configurableVeetaha2020-08-261-47/+28
|
* Merge #5841bors[bot]2020-08-241-0/+8
|\ | | | | | | | | | | | | | | | | | | 5841: Gate stream.pipeline workaround on fixed versions of node r=matklad a=Veetaha Fixes the symptom of https://github.com/cdr/code-server/issues/1810 Original report here: https://github.com/rust-analyzer/rust-analyzer/issues/3167#issuecomment-678390564 Thanks to @hjfreyer for precise investigation :D Co-authored-by: Veetaha <[email protected]>
| * Gate stream.pipeline workaround on fixed versions of nodeVeetaha2020-08-211-0/+8
| |
* | Dont ask me why...Veetaha2020-08-211-1/+0
|/
* Merge #5782bors[bot]2020-08-172-2/+5
|\ | | | | | | | | | | | | | | | | | | 5782: Fix StatusNotification r=matklad a=vsrs This PR fixes the following: As per specification `params` property in [NotificationMessage ](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#notificationMessage) should be `array | object` while RA uses `"loading" | "ready" | "invalid" | "needsReload"`. Co-authored-by: vsrs <[email protected]>
| * Fix StatusNotificationvsrs2020-08-172-2/+5
| |
* | Rename ra_toolchain -> toolchainAleksey Kladov2020-08-121-2/+2
|/
* Merge #5697bors[bot]2020-08-101-8/+2
|\ | | | | | | | | | | | | | | | | | | 5697: Remove workaround for semantic token flickering r=jonas-schievink a=kjeremy See: https://github.com/microsoft/vscode-languageserver-node/issues/576#issuecomment-593384479 This has been fixed since vscode 1.44 Co-authored-by: Jeremy Kolb <[email protected]>
| * Remove 'as any'Jeremy Kolb2020-08-091-1/+1
| |
| * Remove workaround for semantic token flickeringJeremy Kolb2020-08-091-7/+1
| | | | | | | | | | | | See: https://github.com/microsoft/vscode-languageserver-node/issues/576#issuecomment-593384479 This has been fixed since vscode 1.44
* | Fix no inlay hints / unresolved tokens until manual editVeetaha2020-08-081-3/+3
|/ | | | | | | | | | No we return ContentModified during the workspace loading. This signifies the language client to retry the operation (i.e. the client will continue polling the server while it returns ContentModified). I believe that there might be cases of overly big projects where the backoff logic we have setup in `sendRequestWithRetry` (which we use for inlay hints) might bail too early (currently the largest retry standby time is 10 seconds). However, I've tried on one of my project with 500+ dependencies and it is still enough.
* Merge #5513bors[bot]2020-07-311-2/+10
|\ | | | | | | | | | | | | | | | | | | 5513: Try figure out correct workspace in vscode multi root workspace r=vsrs a=urbandove the code to replace the root with the `${workspaceRoot}` arg breaks in multi root workspaces as it needs a qualifier `${workspaceRoot:workspaceName}` This PR attempts to figure out the root workspace - and if it cant find it falls back to the first workspace Co-authored-by: Urban Dove <[email protected]>
| * delete empty lineUrban Dove2020-07-261-1/+0
| |
| * try select correct workspace in vscode multi workspaceUrban Dove2020-07-261-2/+11
| |
* | SSR: Restrict to current selection if anyDavid Lattimore2020-07-292-2/+4
| | | | | | | | | | The selection is also used to avoid unnecessary work, but only to the file level. Further restricting unnecessary work is left for later.
* | SSR: Fix a typescript lint warningDavid Lattimore2020-07-241-1/+1
| |
* | SSR: Pass current file position through to SSR code.David Lattimore2020-07-242-3/+13
|/ | | | In a subsequent commit, it will be used for resolving paths.
* Merge #5480bors[bot]2020-07-231-0/+4
|\ | | | | | | | | | | | | | | | | | | | | 5480: Fix snippetTextEdits applying to other files r=matklad a=TimoFreiberg Fixes #4551 `vscode.window.visibleTextEditors` only contains editors whose contents are being displayed at the moment, so the previous logic only worked if the other file for which a snippetTextEdit is being received was visible in a separate split. I feel that this is a hacky approach, so feel free to reject it for something nicer :) Co-authored-by: Timo Freiberg <[email protected]>
| * Fix snippetTextEdits applying to other filesTimo Freiberg2020-07-221-0/+4
| | | | | | | | | | | | | | vscode.window.visibleTextEditors only contains editors whose contents are being displayed at the moment, so the previous logic only worked if the other file for which a snippetTextEdit is being received was visible in a separate split.
* | ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's ↵James Leitch2020-07-231-0/+1
|/ | | | owner and source. VSCode LSP updated to specify owner.
* Workaround rollup messing up default importsVeetaha2020-07-081-1/+4
|
* Gzip artifactsVeetaha2020-07-072-16/+17
| | | | | | | | | | 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-073-0/+34
|
* Consider EPERM error as other vscode processes using rust-analyzerVeetaha2020-07-071-1/+1
|
* Fix: allow for binaries from $PATH to pass validity checkVeetaha2020-07-061-6/+2
|
* Revert "Dispose logger on extension deactivation"Veetaha2020-07-052-6/+0
| | | | | This reverts commit 13872543e074adc153b440660beda441fd562f53. That commit was wrong because we use-after-free the logger
* Dispose logger on extension deactivationVeetaha2020-07-052-0/+6
|
* Improve client logging (use output channel and more log levels)Veetaha2020-07-054-18/+49
|
* Merge #5202bors[bot]2020-07-033-13/+44
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5202: Runnable env r=matklad a=vsrs This PR adds on option to specify (in the settings.json) environment variables passed to the runnable. The simplest way for all runnables in a bunch: ```jsonc "rust-analyzer.runnableEnv": { "RUN_SLOW_TESTS": "1" } ``` Or it is possible to specify vars more granularly: ```jsonc "rust-analyzer.runnableEnv": [ { // "mask": null, // null mask means that this rule will be applied for all runnables env: { "APP_ID": "1", "APP_DATA": "asdf" } }, { "mask": "test_name", "env": { "APP_ID": "2", // overwrites only APP_ID } } ] ``` You can use any valid RegExp as a mask. Also note that a full runnable name is something like *run bin_or_example_name*, *test some::mod::test_name* or *test-mod some::mod*, so it is possible to distinguish binaries, single tests, and test modules with this masks: `"^run"`, `"^test "` (the trailing space matters!), and `"^test-mod"` respectively. Fixes #4450 I suppose this info should be somewhere in the docs, but unsure where is the best place. Co-authored-by: vsrs <[email protected]>
| * Fix workspaceRootvsrs2020-07-031-1/+3
| |
| * code lintingvsrs2020-07-032-2/+2
| |
| * Add testsvsrs2020-07-033-10/+10
| |
| * Add runnable env support.vsrs2020-07-033-11/+40
| |
* | Pass CodeActionKind through our middleware to populate menusJeremy Kolb2020-07-021-2/+4
|/
* Merge #5188bors[bot]2020-07-023-1/+46
|\ | | | | | | | | | | | | | | 5188: Implement StatusBar r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * Implement StatusBarAleksey Kladov2020-07-023-1/+46
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 04:48:39 +0000