aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | | | Keep VSCode config mostly backwards compatibleEmil Lauridsen2019-12-254-35/+40
| | | | | | | |
* | | | | | | | Re-format VSCode extension changesEmil Lauridsen2019-12-252-19/+20
| | | | | | | |
* | | | | | | | Re-implement status display using LSP 3.15 progress eventEmil Lauridsen2019-12-252-0/+51
| | | | | | | |
* | | | | | | | Remove cargo watch supporting code and tests from vscode extensionEmil Lauridsen2019-12-2514-1684/+0
| | | | | | | |
* | | | | | | | Configuration plumbing for cargo watcherEmil Lauridsen2019-12-253-74/+28
| | | | | | | |
* | | | | | | | Remove cargo-watch from vscode extension.Emil Lauridsen2019-12-256-454/+1
| |_|_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | Still keeps tests around for reference when porting them to rust
* | | | | | | Protect against null as revealed by `npm test`kjeremy2019-12-201-2/+7
| | | | | | |
* | | | | | | Update to latest packageskjeremy2019-12-202-33/+33
| | | | | | |
* | | | | | | Use substr instead of endswithEdwin Cheng2019-12-181-3/+3
| | | | | | |
* | | | | | | Add testsEdwin Cheng2019-12-182-0/+295
| | | | | | |
* | | | | | | Add macro span handlingEdwin Cheng2019-12-181-0/+38
| | | | | | |
* | | | | | | Merge #2583bors[bot]2019-12-173-3/+47
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2583: Use prettier settings in ts-lint r=matklad a=edwin0cheng This PR add `tslint-plugin-prettier` extension in ts-lint, which "runs prettier rules as tslint rules." and remove `quotemark` from ts-lint and let prettier to handle it. And also fix #2515 Co-authored-by: Edwin Cheng <[email protected]>
| * | | | | | | use pretter settings in ts-lintEdwin Cheng2019-12-173-3/+47
| | | | | | | |
* | | | | | | | Merge #2580bors[bot]2019-12-171-4/+4
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2580: Fix highlighting token names r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | | | Fix highlighting token namesAleksey Kladov2019-12-171-4/+4
| | | | | | | | |
* | | | | | | | | Merge #2568bors[bot]2019-12-173-2/+18
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2568: Add option to disable all-targets. r=matklad a=pftbest Can be useful in embedded. Co-authored-by: Vadzim Dambrouski <[email protected]>
| * | | | | | | | | Fix formattingVadzim Dambrouski2019-12-161-2/+1
| | | | | | | | | |
| * | | | | | | | | Add option to disable all-targets.Vadzim Dambrouski2019-12-153-1/+18
| | |/ / / / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | Can be useful in embedded.
* | | | | | | | | Merge #2571bors[bot]2019-12-171-1/+1
|\ \ \ \ \ \ \ \ \ | |_|/ / / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2571: Fixed a typo in settings r=matklad a=omerbenamram @lnicola found a typo in the description for one of the settings introduced in #2559. Co-authored-by: Omer Ben-Amram <[email protected]>
| * | | | | | | | Fixed a typoOmer Ben-Amram2019-12-161-1/+1
| |/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | thanks @lnicola
* / / / / / / / 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
| |_|_|_|/ |/| | | |
* | | | | Add rust-analyzer-expand-macro function for EmacsFlorian Diebold2019-11-201-0/+28
| | | | |
* | | | | 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
| | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 04:06:55 +0000