aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
* vscode: remove logging from inlays, run fix lint issuesVeetaha2020-03-071-18/+7
|
* vscode: remove logic for caching editors as per @matkladVeetaha2020-03-071-222/+136
|
* vscode: prerefactor util.ts and ctx.tsVeetaha2020-03-072-10/+14
|
* vscode: refresh all editors on text changes, simplify inlays apiVeetaha2020-03-071-13/+11
|
* vscode: add dat semicolonVeetaha2020-03-071-1/+1
|
* vscode: simpifyVeetaha2020-03-071-5/+1
|
* vscode: redesign inlay hints to be capable of handling multiple editorsVeetaha2020-03-072-106/+273
|
* vscode: extract Type and Param hint cases of InlayHint at type level (needed ↵Veetaha2020-03-071-8/+14
| | | | further)
* Merge #3388bors[bot]2020-03-035-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: ![image](https://user-images.githubusercontent.com/131878/75628802-b1ac1900-5bdc-11ea-8c26-6722d8e38371.png) After the change: ![image](https://user-images.githubusercontent.com/131878/75628831-e91ac580-5bdc-11ea-9039-c6b4ffbdb2be.png) 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 documentJulien Roncaglia2020-03-025-24/+25
| | | | | | | | Also move visibleRustEditors to Ctx
| * Remove inlay in diff viewsJulien Roncaglia2020-03-011-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 breaksAleksey Kladov2020-03-021-4/+6
|/
* vscode: simplify assert.eq() to assert() as per matkladVeetaha2020-02-282-15/+4
|
* vscode: add dat semicolonVeetaha2020-02-281-1/+1
|
* vscode: add equality assertionVeetaha2020-02-282-2/+12
|
* vscode: rename nodeAssert -> nativeAssertVeetaha2020-02-281-2/+2
|
* vscode: add error loging on failed assertionVeetaha2020-02-281-1/+6
|
* vscode: migrate to more type-safe assert implVeetaha2020-02-283-8/+10
|
* Reset fontStyle for inlay hintsAleksey Kladov2020-02-281-0/+2
| | | | Otherwise, we get bold hints on `true` and `false`
* Fix lintAleksey Kladov2020-02-271-1/+1
|
* Fix flickering with new syntax highlightingAleksey Kladov2020-02-271-1/+9
|
* Config to switch to semantic tokensAleksey Kladov2020-02-263-3/+10
|
* Merge pull request #3321 from kjeremy/semantic-clientAleksey Kladov2020-02-261-0/+3
|\ | | | | Enable SemanticTokens on the client
| * Enable SemanticTokens on the clientJeremy Kolb2020-02-261-0/+3
| | | | | | | | This will crash the extension on stable and insiders without the "--enable-proposed-api matklad.rust-analyzer" command line switch.
* | Remove unnecessary depAleksey Kladov2020-02-261-13/+8
|/
* Merge #3295bors[bot]2020-02-252-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 matkladVeetaha2020-02-241-3/+5
| |
| * vscode: remove type assertionVeetaha2020-02-241-1/+1
| |
| * add error handling to fetchArtifactReleaseInfo(), throw Error when no ↵Veetaha2020-02-241-19/+37
| | | | | | | | artifact found
* | vscode: migrate rust-analyzer-api to import * as lc as per matklad and kjeremyVeetaha2020-02-241-23/+23
| |
* | vscode: run fmtVeetaha2020-02-241-1/+1
| |
* | vscode: migrate inlay_hints to rust-analyzer-api.tsVeetaha2020-02-242-31/+16
| |
* | vscode: migrate syntax_tree to rust-analyzer-api.tsVeetaha2020-02-241-20/+7
| |
* | vscode: migrate ssr to rust-analyzer-api.tsVeetaha2020-02-241-11/+5
| |
* | vscode: migrate runnables to rust-analyzer-api.tsVeetaha2020-02-241-22/+7
| |
* | vscode: migrate parent_module to rust-analyzer-api.tsVeetaha2020-02-241-7/+3
| |
* | vscode: migrate on_enter to rust-analyzer-api.tsVeetaha2020-02-241-14/+7
| |
* | vscode: migrate matching_brace to rust-analyzer-api.tsVeetaha2020-02-241-12/+3
| |
* | vscode: migrate join_lines to rust-analyzer-api.tsVeetaha2020-02-241-13/+4
| |
* | vscode: migrate collectGarbage to rust-analyzer-api.tsVeetaha2020-02-241-5/+4
| |
* | vscode: migrate expand_macro to rust-analyzer-api.tsVeetaha2020-02-241-13/+5
| |
* | vscode: migrate analyzer_status to rust-analyzer-api.tsVeetaha2020-02-241-4/+2
| |
* | vscode: migrate highlighting to rust-analyzer-api.tsVeetaha2020-02-241-39/+21
| |
* | vscode: migrate source_cnage.rs to rust-analyzer-api.rsVeetaha2020-02-241-7/+2
| |
* | vscode: create rust-analyzer-api.tsVeetaha2020-02-241-0/+117
|/
* CleanpAleksey Kladov2020-02-241-2/+2
|
* Merge #3290bors[bot]2020-02-241-0/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | 3290: Don't block onEnter if request fails r=matklad a=matklad closes #3286 bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Don't block onEnter if request failsAleksey Kladov2020-02-241-0/+6
| | | | | | | | closes #3286
* | Merge #3288bors[bot]2020-02-241-2/+5
|\ \ | |/ |/| | | | | | | | | | | 3288: Quick fix circular json error when sanity-check fails r=matklad a=Veetaha Related issue: #3280 Co-authored-by: Veetaha <[email protected]>
| * Quick fix circular json error when sanity-check failsVeetaha2020-02-241-2/+5
| | | | | | Related issue: #3280