| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fixup! feat: add debug code lens | Hannes De Valkeneer | 2020-03-12 | 1 | -6/+1 |
| | | | | | avoid repetition of `--no-run` | ||||
| * | fixup! feat: add debug code lens | Hannes De Valkeneer | 2020-03-12 | 1 | -2/+1 |
| | | |||||
| * | feat: add debug code lens | Hannes De Valkeneer | 2020-03-11 | 3 | -3/+29 |
| | | | | | Refs #3539 | ||||
| * | Add additional_outdirs in config | Edwin Cheng | 2020-03-10 | 2 | -0/+2 |
| | | |||||
| * | vscode: groupd updates-related config under `updates` section as per @matklad | Veetaha | 2020-03-09 | 1 | -1/+1 |
| | | |||||
| * | vscode: fix inversion of askBeforeDownload | Veetaha | 2020-03-08 | 1 | -1/+1 |
| | | |||||
| * | vscode: rename alwaysDownloadServer -> askBeforeDownload | Veetaha | 2020-03-08 | 1 | -1/+1 |
| | | | | | | | | | | | | The new name seems much simpler and it doesn't limit this config value only to downloading the server binary. Thus we wouldn't need to create another config properties to handle other downloads whatsoever. Anyway, I believe (heuristically) that most of the users would want to set "askBeforeDownload": false once and never bother clicking on the notification again (because otherwise there is no big point in installing rust-analyzer if it cannot install the server) | ||||
| * | vscode: care about alwaysDownloadServer option before asking | Veetaha | 2020-03-07 | 3 | -23/+31 |
| | | | | | | | | Also renamed BinarySource to ArtifactSource in anticipation of nightlies installation that requires downloading not a binary itself but .vsix package, thus generalized to `artifact` term | ||||
| * | vscode: post refactor HintsUpdater (simplify create() -> constructor call) | Veetaha | 2020-03-07 | 1 | -16/+10 |
| | | |||||
| * | vscode: more privacy for HintsUpdater | Veetaha | 2020-03-07 | 1 | -1/+1 |
| | | |||||
| * | vscode: remove logging from inlays, run fix lint issues | Veetaha | 2020-03-07 | 1 | -18/+7 |
| | | |||||
| * | vscode: remove logic for caching editors as per @matklad | Veetaha | 2020-03-07 | 1 | -222/+136 |
| | | |||||
| * | vscode: prerefactor util.ts and ctx.ts | Veetaha | 2020-03-07 | 2 | -10/+14 |
| | | |||||
| * | vscode: refresh all editors on text changes, simplify inlays api | Veetaha | 2020-03-07 | 1 | -13/+11 |
| | | |||||
| * | vscode: add dat semicolon | Veetaha | 2020-03-07 | 1 | -1/+1 |
| | | |||||
| * | vscode: simpify | Veetaha | 2020-03-07 | 1 | -5/+1 |
| | | |||||
| * | vscode: redesign inlay hints to be capable of handling multiple editors | Veetaha | 2020-03-07 | 2 | -106/+273 |
| | | |||||
| * | vscode: extract Type and Param hint cases of InlayHint at type level (needed ↵ | Veetaha | 2020-03-07 | 1 | -8/+14 |
| | | | | | further) | ||||
| * | Merge #3388 | bors[bot] | 2020-03-03 | 5 | -15/+25 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3388: Remove inlay hint in diff views r=matklad a=vbfox If the left side of a diff view that contain the old version of the file apply inlays they are misplaced and produce a weird display:  After the change:  The detection is done by blacklisting the url schemes used by git and subversion scm extensions, whitelisting `file` is also possible but neither is perfect as VSCode now support both pluggable scm extensions and pluggable remote filesystems. But I suspect that the list of scm extensions is more easily manageable. **Note**: I can rebase on #3378 if needed as it touches the same lines of code Co-authored-by: Julien Roncaglia <[email protected]> | ||||
| | * | Centralize the check for languageId on document | Julien Roncaglia | 2020-03-02 | 5 | -24/+25 |
| | | | | | | | | | Also move visibleRustEditors to Ctx | ||||
| | * | Remove inlay in diff views | Julien Roncaglia | 2020-03-01 | 1 | -1/+10 |
| | | | | | | | | | | | | | | | | | If the left side of a diff view that contain the old version of the file apply inlays they are misplaced. The detection is done by blacklisting the url schemes used by git and subversion scm extensions. | ||||
| * | | Don't fail loudly if the old highlighting breaks | Aleksey Kladov | 2020-03-02 | 1 | -4/+6 |
| |/ | |||||
| * | vscode: simplify assert.eq() to assert() as per matklad | Veetaha | 2020-02-28 | 2 | -15/+4 |
| | | |||||
| * | vscode: add dat semicolon | Veetaha | 2020-02-28 | 1 | -1/+1 |
| | | |||||
| * | vscode: add equality assertion | Veetaha | 2020-02-28 | 2 | -2/+12 |
| | | |||||
| * | vscode: rename nodeAssert -> nativeAssert | Veetaha | 2020-02-28 | 1 | -2/+2 |
| | | |||||
| * | vscode: add error loging on failed assertion | Veetaha | 2020-02-28 | 1 | -1/+6 |
| | | |||||
| * | vscode: migrate to more type-safe assert impl | Veetaha | 2020-02-28 | 3 | -8/+10 |
| | | |||||
| * | Reset fontStyle for inlay hints | Aleksey Kladov | 2020-02-28 | 1 | -0/+2 |
| | | | | | Otherwise, we get bold hints on `true` and `false` | ||||
| * | Fix lint | Aleksey Kladov | 2020-02-27 | 1 | -1/+1 |
| | | |||||
| * | Fix flickering with new syntax highlighting | Aleksey Kladov | 2020-02-27 | 1 | -1/+9 |
| | | |||||
| * | Config to switch to semantic tokens | Aleksey Kladov | 2020-02-26 | 3 | -3/+10 |
| | | |||||
| * | Merge pull request #3321 from kjeremy/semantic-client | Aleksey Kladov | 2020-02-26 | 1 | -0/+3 |
| |\ | | | | | Enable SemanticTokens on the client | ||||
| | * | Enable SemanticTokens on the client | Jeremy Kolb | 2020-02-26 | 1 | -0/+3 |
| | | | | | | | | | This will crash the extension on stable and insiders without the "--enable-proposed-api matklad.rust-analyzer" command line switch. | ||||
| * | | Remove unnecessary dep | Aleksey Kladov | 2020-02-26 | 1 | -13/+8 |
| |/ | |||||
| * | Merge #3295 | bors[bot] | 2020-02-25 | 2 | -20/+40 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | 3295: Refactoring fetchArtifactReleaseInfo() r=matklad a=Veetaha https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-unnecessary-type-assertion.md I fact this rule doesn't work when you put an unnecessary non-null assertion in an expression (as we had `(awat f())!`, but it is useful in other cases... Closes #3295, i guess... Co-authored-by: Veetaha <[email protected]> | ||||
| | * | vscode: wrap non-single-line if body with curlies as per matklad | Veetaha | 2020-02-24 | 1 | -3/+5 |
| | | | |||||
| | * | vscode: remove type assertion | Veetaha | 2020-02-24 | 1 | -1/+1 |
| | | | |||||
| | * | add error handling to fetchArtifactReleaseInfo(), throw Error when no ↵ | Veetaha | 2020-02-24 | 1 | -19/+37 |
| | | | | | | | | | artifact found | ||||
| * | | vscode: migrate rust-analyzer-api to import * as lc as per matklad and kjeremy | Veetaha | 2020-02-24 | 1 | -23/+23 |
| | | | |||||
| * | | vscode: run fmt | Veetaha | 2020-02-24 | 1 | -1/+1 |
| | | | |||||
| * | | vscode: migrate inlay_hints to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 2 | -31/+16 |
| | | | |||||
| * | | vscode: migrate syntax_tree to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -20/+7 |
| | | | |||||
| * | | vscode: migrate ssr to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -11/+5 |
| | | | |||||
| * | | vscode: migrate runnables to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -22/+7 |
| | | | |||||
| * | | vscode: migrate parent_module to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -7/+3 |
| | | | |||||
| * | | vscode: migrate on_enter to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -14/+7 |
| | | | |||||
| * | | vscode: migrate matching_brace to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -12/+3 |
| | | | |||||
| * | | vscode: migrate join_lines to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -13/+4 |
| | | | |||||
| * | | vscode: migrate collectGarbage to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -5/+4 |
| | | | |||||
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |