aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
* Bump chalk to use latest git to get fixCasey Primozic2020-10-061-1/+1
| | | | * Chalk very recently (like an hour ago) merged a fix that prevents rust analyzer from panicking. This allows it to be usable again for code that hits those situations. See #6134, #6145, Probably #6120
* Make ImportPrefix a configuration optionLukas Wirth2020-10-051-1/+16
|
* Support 'runnables' options in the vs code extensionIgor Aleksanov2020-10-025-2/+31
|
* Extend **Status** command to also show dep info for the fileAleksey Kladov2020-09-292-8/+16
| | | | This should help with troubleshooting wrong project configuration
* Make method references CodeLens off by default.vsrs2020-09-291-1/+1
|
* Add method references CodeLensvsrs2020-09-292-0/+6
|
* Fix lintMatthias Einwag2020-09-231-1/+1
|
* Move unlink on download into download functionMatthias Einwag2020-09-232-11/+11
| | | | | 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-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-232-0/+13
|
* 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
|
* Document "consuming" semantic tokens modifierVeetaha2020-09-151-0/+4
|
* Fix delimiter in SSR exampleLaurențiu Nicola2020-09-151-1/+1
|
* Merge #5985bors[bot]2020-09-141-0/+15
|\ | | | | | | | | | | | | | | 5985: Make MergeBehaviour configurable r=jonas-schievink a=Veykril This should make the newly implemented `MergeBehaviour` for import insertion configurable as roughly outlined in https://github.com/rust-analyzer/rust-analyzer/pull/5935#issuecomment-685834257. For the config name and the like I just picked what came to mind so that might be up for bikeshedding. Co-authored-by: Lukas Wirth <[email protected]>
| * Make MergeBehaviour configurableLukas Wirth2020-09-121-0/+15
| |
* | Bump node-fetch from 2.6.0 to 2.6.1 in /editors/codedependabot[bot]2020-09-122-4/+4
|/ | | | | | | | Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 2.6.0 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1) Signed-off-by: dependabot[bot] <[email protected]>
* Move to vscode-languageclient 7.0.0-next.9kjeremy2020-09-026-34/+25
| | | | Stabilizes call hierarchy and semantic tokens features.
* Update the rest of our node packageskjeremy2020-09-012-137/+163
|
* Bump minimum vscode to 1.47kjeremy2020-09-012-21/+21
|
* Upgrade mocha from `npm audit fix`kjeremy2020-09-012-69/+211
|
*-. 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
| |/
* / Add rust-analyzer.checkOnSave.target to package.jsonLaurențiu Nicola2020-08-281-0/+8
|/
* Make inlay hints colors more configurableVeetaha2020-08-262-49/+93
|
* 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
|/
* Align diagnostics config with the rest of rust-analyzerAleksey Kladov2020-08-181-6/+6
|
* Merge #5682bors[bot]2020-08-181-0/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 5682: Add an option to disable diagnostics r=matklad a=popzxc As far as I know, currently it's not possible to disable a selected type of diagnostics provided by `rust-analyzer`. This causes an inconvenient situation with a false-positive warnings: you either have to disable all the diagnostics, or you have to ignore these warnings. There are some open issues related to this problem, e.g.: https://github.com/rust-analyzer/rust-analyzer/issues/5412, https://github.com/rust-analyzer/rust-analyzer/issues/5502 This PR attempts to make it possible to selectively disable some diagnostics on per-project basis. Co-authored-by: Igor Aleksanov <[email protected]>
| * Merge branch 'master' into add-disable-diagnosticsIgor Aleksanov2020-08-141-2/+2
| |\
| * | Restore final newline in package.jsonIgor Aleksanov2020-08-131-1/+1
| | |
| * | Merge branch 'master' into add-disable-diagnosticsIgor Aleksanov2020-08-123-12/+6
| |\ \
| * | | Add a configuration option for the vscode extensionIgor Aleksanov2020-08-121-1/+10
| | | |
| | | |
| \ \ \
*-. \ \ \ Merge #5776 #5780bors[bot]2020-08-171-0/+3
|\ \ \ \ \ | | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5776: Fix eslint errors on .eslintrc.js and rollup.config.js r=matklad a=fuafa Eslint complains if these two files does not include in the `tsconfig.json`. ``` Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser. The file does not match your project config: .eslintrc.js. The file must be included in at least one of the projects provided.eslint ``` ![image](https://user-images.githubusercontent.com/20750310/90338269-176d4f80-e01b-11ea-8710-3ea817b235d2.png) 5780: Fixup whitespace when adding missing impl items r=matklad a=jDomantas Generate properly formatted whitespace when adding impl items - with an empty line between items and removing extra whitespace that often appears at the end. This is my first time working on rust analyzer so I'm not very familiar with its internal APIs. If there's a better way to do such syntax tree editing I'd be glad to hear it. Co-authored-by: xiaofa <[email protected]> Co-authored-by: jDomantas <[email protected]>
| * / | | Fix eslint errors on .eslintrc.js and rollup.config.jsxiaofa2020-08-161-0/+3
| |/ / /
* | | | 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.