aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
* Cleanup highlighting tagsAleksey Kladov2020-02-281-17/+70
|
* add more tagsAleksey Kladov2020-02-281-9/+0
|
* Map builtinAleksey Kladov2020-02-271-0/+6
|
* Set attr scopeAleksey Kladov2020-02-271-0/+6
|
* Map unsafe keywordAleksey Kladov2020-02-271-0/+6
|
* Fix styleAleksey Kladov2020-02-271-1/+1
|
* Fix lintAleksey Kladov2020-02-271-1/+1
|
* Actually gate CI on eslintAleksey Kladov2020-02-271-1/+2
|
* Merge #3339bors[bot]2020-02-271-1/+9
|\ | | | | | | | | | | | | | | | | | | | | 3339: Fix flickering with new syntax highlighting r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Fix flickering with new syntax highlightingAleksey Kladov2020-02-271-1/+9
| |
* | Merge #3308bors[bot]2020-02-271-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3308: vscode: fix vscode-vim keybindings conflict r=matklad a=Veetaha Closes #3013 I hope vscode-vim extension overrides the `type` command so that it prevents some keypresses to reach the text document editor. It conflicts with our `onEnter` keybinding that is used to support automatic doc comments extending and indentation insertion. The VSCode-native way to implement this would be to use regular expressions, but as per matklad it is considered not acceptable for the language server. Thus we implement it via a `Enter` keybinding that invokes our `onEnter` command which does it via the language-server. At the end of the day we may only apply ad hoc workarounds for conflicting extensions. But vscode has another bug for that. You either cannot use parantheses in `when` condition of a keybinding or it just malfunctions. See an issue about that here: https://github.com/microsoft/vscode/issues/91473 To get the ultimate context, follow this [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Enhanced.20typing) Co-authored-by: Veetaha <[email protected]>
| * vscode: fix vscode-vim keybindings conflictVeetaha2020-02-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vscode-vim extension overrides the `type` command so that it prevents some keypresses to reach the text document editor. It conflicts with our `onEnter` keybinding that is used to support automatic doc comments extending and indentation insertion. The VSCode-native way to implement this would be to use regular expressions, but as per matklad it is considered not acceptable for the language server. Thus we implement it via a `Enter` keybinding that invokes our `onEnter` command which sends a request to rust-analyzer process and applies the appropriate source change recieved from it. At the end of the day we may only apply ad hoc workarounds for conflicting extensions. But vscode has another bug for that. You either cannot use parantheses in `when` condition of a keybinding or it just malfunctions. See an issue about that here: https://github.com/microsoft/vscode/issues/91473 To get the ultimate context, follow this zulip thread: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Enhanced.20typing
* | Color constantsAleksey Kladov2020-02-271-0/+9
| |
* | Better highlightign APIAleksey Kladov2020-02-271-0/+19
| |
* | wipAleksey Kladov2020-02-261-0/+14
| |
* | Config to switch to semantic tokensAleksey Kladov2020-02-264-3/+15
| |
* | Merge pull request #3321 from kjeremy/semantic-clientAleksey Kladov2020-02-262-0/+4
|\ \ | | | | | | Enable SemanticTokens on the client
| * | Enable SemanticTokens on the clientJeremy Kolb2020-02-262-0/+4
| |/ | | | | | | 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-263-26/+8
|/
* Merge #3295bors[bot]2020-02-253-21/+42
|\ | | | | | | | | | | | | | | | | | | | | | | 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-242-2/+3
| |
| * add error handling to fetchArtifactReleaseInfo(), throw Error when no ↵Veetaha2020-02-241-19/+37
| | | | | | | | artifact found
* | Merge #3299bors[bot]2020-02-2515-198/+203
|\ \ | | | | | | | | | | | | | | | | | | | | | 3299: vscode: migrate to request type api r=matklad a=Veetaha More type-safety to the god of type-safety. Co-authored-by: Veetaha <[email protected]>
| * | 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
| |/
* / vscode: bump TypeScript versionVeetaha2020-02-242-4/+4
|/
* 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
* | Don't break onEnter if rust-analyzer fails to startAleksey Kladov2020-02-241-0/+23
|/ | | | closes #3253
* vscode: gracefully handle cancellation errorsVeetaha2020-02-234-44/+60
|
* Extract client-side loggingAleksey Kladov2020-02-2210-21/+51
|
* vscode: migrate to tripple equalsVeetaha2020-02-224-9/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-19 12:59:23 +0000