aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
* Fix highlighting token namesAleksey Kladov2019-12-171-4/+4
|
* Default to client watching on VS CodeAleksey Kladov2019-12-172-3/+3
|
* Merge #2565bors[bot]2019-12-151-3/+8
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2565: Fixed syntax highlighting not refreshing on windows. r=matklad a=omerbenamram I was encoutering the same probelm described in #1690. It seems that events initiated by the frontend with `rust-analyzer/decorationsRequest` would go through. So whenever a user switches tabs, highlighting will update. However, when decorations are initiated by a notification with `rust-analyzer/publishDecorations`, it would fail on this check here https://github.com/rust-analyzer/rust-analyzer/blob/6cbd8a4a4bbca8a7656df9f3ef849acebbf9ef9b/editors/code/src/notifications/publish_decorations.ts#L15 (`targetEditor` will always be `undefined`). This is because it's trying to match the uri `rust-analyzer` sends (which uses an uppercase drive letter) to the uri provided at `editor.document.uri.toString()`, which is both escaped (uses `%3a` for `:`), and uses a lowercase letter drive. Aparrently this was an issue for some other extensions aswell - https://github.com/Microsoft/vscode/issues/68325. But this is the defined behavior - https://github.com/microsoft/vscode/blob/c110d84460b3e45842a8fe753562341003595e1d/src/vs/vscode.d.ts#L1304 This fix is only relevant for windows. I've opted for a server-side fix, since rust will always return uppercase letters for drives, there seems to be no other easy solution than manipulating the Url string before sending it to the frontend. Closes #1690. Co-authored-by: Omer Ben-Amram <[email protected]>
| * `npm run fix`Omer Ben-Amram2019-12-151-8/+6
| |
| * fixed commentOmer Ben-Amram2019-12-151-2/+1
| |
| * Lowercase drive letters on windows before sending to extension.Omer Ben-Amram2019-12-151-2/+1
| |
| * make drive comparison case-insensitive.Omer Ben-Amram2019-12-151-1/+10
| |
* | Properly format jsonOliver Scherer2019-12-151-9/+11
| |
* | Add a rudimentary json regex to get at information like `endLine`Oliver Scherer2019-12-151-0/+20
|/
* Merge branch 'refs/heads/master' into feature/granular-scopesOmer Ben-Amram2019-12-143-13/+80
|\
| * Enable `allFeatures` by default and fix lintsoxalica2019-12-132-10/+17
| |
| * Support setting cargo featuresoxalica2019-12-133-13/+73
| |
* | removed `type.alias`Omer Ben-Amram2019-12-142-0/+10
| |
* | added decorationsOmer Ben-Amram2019-12-142-1/+61
|/
* Enable noFallthroughCasesInSwitch option for vscode extensionTetsuharu OHZEKI2019-12-111-1/+2
|
* Enable noImplicitReturns option for vscode extensionTetsuharu OHZEKI2019-12-115-12/+20
|
* Enable noUnusedParameters option for vscode extensionTetsuharu OHZEKI2019-12-115-5/+8
|
* Use ES2018 for vscode extensionTetsuharu OHZEKI2019-12-111-2/+2
| | | | | | | Today's latest vscode v1.40 (Node.jsv12.4/V8 v7.6) supports ES2018 features natively. We don't have to transform codes to ES6.
* Code: enable prettier trailing commasLaurențiu Nicola2019-12-0931-232/+233
|
* Allow disabling sysrootAleksey Kladov2019-12-092-1/+7
| | | | Might be helpful for debugging
* Add rollup sourcemap and fix launch.jsonEdwin Cheng2019-12-083-0/+57
|
* Merge #2508bors[bot]2019-12-081-5/+9
|\ | | | | | | | | | | | | | | | | | | | | | | 2508: Code: don't check for ra_lsp_server on Windows r=matklad a=lnicola Workaround for https://github.com/rust-analyzer/rust-analyzer/pull/2503#issuecomment-562980020. ~~(not yet tested on Windows)~~ We can't run `ra_lsp_server --version` right now because the server doesn't seem to handle arguments (so it hangs). Co-authored-by: Laurențiu Nicola <[email protected]>
| * Code: don't check for ra_lsp_server on WindowsLaurențiu Nicola2019-12-081-5/+9
| |
* | Code: bump depsLaurențiu Nicola2019-12-084-418/+253
|/
* Code: check whether the LSP binary is in PATHLaurențiu Nicola2019-12-084-6/+23
|
* Fix npm vulnerability warningEdwin Cheng2019-12-061-3/+3
|
* rename ra_ide_api -> ra_ideAleksey Kladov2019-11-271-0/+0
|
* Merge pull request #2297 from kiljacken/masterAleksey Kladov2019-11-202-13/+2
|\ | | | | Add fancy truncation of type hints.
| * Move type inlay hint truncation to language serverEmil Lauridsen2019-11-192-13/+2
| | | | | | | | | | | | | | | | | | | | | | | | This commit implements a general truncation framework for HirFormatter that keeps track of how much has been output so far. This information can then be used to perform truncation inside the language server, instead of relying on the client. Initial support is implemented for truncating types hints using the maxInlayHintLength server config option. The existing solution in the VSCode extension has been removed in favor of letting the server truncate type hints.
* | Minor fix for outpu text formatingEdwin Cheng2019-11-191-1/+1
| |
* | Use DocumentProvider instead of HoverEdwin Cheng2019-11-193-33/+75
| |
* | Change return type of expand_macroEdwin Cheng2019-11-191-5/+8
| |
* | Fix npm formattingEdwin Cheng2019-11-192-14/+14
| |
* | Add recursive expand in vscodeEdwin Cheng2019-11-193-5/+62
|/
* Fix formatoxalica2019-11-161-1/+3
|
* Check exit code of `cargo watch`oxalica2019-11-151-3/+3
|
* Handle errors when `cargo watch` failsoxalica2019-11-151-0/+5
|
* Add link to the vscode VIM extension compatibility warning.krk2019-10-301-1/+1
|
* document feature flagsAleksey Kladov2019-10-253-14/+0
|
* Merge #1980bors[bot]2019-10-233-1/+28
|\ | | | | | | | | | | | | | | 1980: Shorten inline type hints r=matklad a=detrumi Implements #1946 Co-authored-by: Wilco Kusee <[email protected]>
| * Do not truncate the rangeWilco Kusee2019-10-231-30/+10
| |
| * Make inlay hint length configurableWilco Kusee2019-10-183-14/+37
| |
| * Truncate hints longer than 20 charactersWilco Kusee2019-10-101-4/+28
| |
* | Adds config option for cargo-watch `--ignore` flagRoberto Vidal2019-10-173-2/+21
| |
* | Add rust-analyzer.showWorkspaceLoadedNotification to package.jsonLaurențiu Nicola2019-10-171-0/+5
| |
* | Merge #1984bors[bot]2019-10-102-29/+21
|\ \ | | | | | | | | | | | | | | | | | | | | | 1984: Bump rollup and vsce r=matklad a=kjeremy I got sick of the vsce warning on install and noticed that rollup was also out of date. Co-authored-by: kjeremy <[email protected]>
| * | Bump rollup and vscekjeremy2019-10-102-29/+21
| |/
* / engine.vscode and @types/vscode should matchkjeremy2019-10-101-1/+1
|/
* Fixarsdragonfly2019-09-281-3/+1
|
* Fix testsarsdragonfly2019-09-272-6/+5
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 10:53:46 +0000