aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge #6274bors[bot]2020-10-191-1/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | 6274: Check cargoExtraArgs for undefined before using r=matklad a=feileacan Fixes #6273 Co-authored-by: feileacan <[email protected]>
| * | Check cargoExtraArgs for undefined before usingfeileacan2020-10-181-1/+3
| | |
* | | fix: prevent unwanted interpolation scopesDusty Pomerleau2020-10-181-14/+6
|/ /
* / fix: prevent early termination of raw strings with hashDusty Pomerleau2020-10-161-3/+22
|/
* Insert a ZWNJ before type hintsLaurențiu Nicola2020-10-151-2/+4
|
* Fix resolveCodeAction requestLaurențiu Nicola2020-10-131-2/+2
|
* Merge #6137bors[bot]2020-10-121-684/+1041
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6137: add a new TextMate grammar r=matklad a=dustypomerleau Thanks to everyone working hard on Rust Analyzer - my impression is that it's quickly becoming the community default. I think it would be helpful to have a more robust TextMate grammar to fall back on, for those who wish to disable semantic highlighting for any reason. It should allow theming of punctuation, and provide scopes for all tokens on the page. This can be done at zero cost to those who enable semantic highlighting, as the TextMate scopes will be invisible to those users. I can see a couple ways of accomplishing this: 1. Ship a new grammar by merging this PR. 1. Ship no TextMate grammar at all (like the [Rust](https://marketplace.visualstudio.com/items?itemName=rust-lang.rust) extension), and allow users to install a separate extension that provides the grammar of their choice (I have released this one as [Rust Syntax](https://marketplace.visualstudio.com/items?itemName=dustypomerleau.rust-syntax)). If no grammar were installed, they would simply fall back to the default grammar provided by their editor. In the case of VS Code, the default grammar already matches what is currently being shipped, so users who choose not to override it would see no difference. I have tried to choose sensible default scopes, in the hopes that a wider variety of themes would work out of the box with Rust, even if those themes do not yet supply scopes for semantic highlighting. There is definitely some interest in using this grammar with Rust Analyzer, as this was the very first issue after the syntax extension was shipped: https://github.com/dustypomerleau/rust-syntax/issues/1. I considered simply using an alternative grammar alongside Rust Analyzer, but this doesn't seem possible. When RA starts, any existing grammar/extension is overridden, and I haven't been able to find a workaround. Co-authored-by: Dusty Pomerleau <[email protected]>
| * add new TextMate grammarDusty Pomerleau2020-10-111-684/+1041
| |
* | Differentiate method/tymethod by determining 'defaultness'Zac Pullar-Strecker2020-10-081-1/+1
| | | | | | | | | | | | | | | | | | Currently a method only has defaultness if it is a provided trait method, but this will change when specialisation is available and may need to become a concept known to hir. I opted to go for a 'fewest changes' approach given specialisation is still under development.
* | Code reorganisation and field supportZac Pullar-Strecker2020-10-082-4/+4
| |
* | Changes from reviewZac Pullar-Strecker2020-10-081-10/+1
| |
* | WIP: Command to open docs under cursorZac Pullar-Strecker2020-10-084-2/+44
|/
* 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
| |\
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-01 22:45:27 +0000