Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add option to disable all-targets. | Vadzim Dambrouski | 2019-12-15 | 3 | -1/+18 |
| | | | | Can be useful in embedded. | ||||
* | Merge #2565 | bors[bot] | 2019-12-15 | 1 | -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-Amram | 2019-12-15 | 1 | -8/+6 |
| | | |||||
| * | fixed comment | Omer Ben-Amram | 2019-12-15 | 1 | -2/+1 |
| | | |||||
| * | Lowercase drive letters on windows before sending to extension. | Omer Ben-Amram | 2019-12-15 | 1 | -2/+1 |
| | | |||||
| * | make drive comparison case-insensitive. | Omer Ben-Amram | 2019-12-15 | 1 | -1/+10 |
| | | |||||
* | | Properly format json | Oliver Scherer | 2019-12-15 | 1 | -9/+11 |
| | | |||||
* | | Add a rudimentary json regex to get at information like `endLine` | Oliver Scherer | 2019-12-15 | 1 | -0/+20 |
|/ | |||||
* | Merge branch 'refs/heads/master' into feature/granular-scopes | Omer Ben-Amram | 2019-12-14 | 3 | -13/+80 |
|\ | |||||
| * | Enable `allFeatures` by default and fix lints | oxalica | 2019-12-13 | 2 | -10/+17 |
| | | |||||
| * | Support setting cargo features | oxalica | 2019-12-13 | 3 | -13/+73 |
| | | |||||
* | | removed `type.alias` | Omer Ben-Amram | 2019-12-14 | 2 | -0/+10 |
| | | |||||
* | | added decorations | Omer Ben-Amram | 2019-12-14 | 2 | -1/+61 |
|/ | |||||
* | Enable noFallthroughCasesInSwitch option for vscode extension | Tetsuharu OHZEKI | 2019-12-11 | 1 | -1/+2 |
| | |||||
* | Enable noImplicitReturns option for vscode extension | Tetsuharu OHZEKI | 2019-12-11 | 5 | -12/+20 |
| | |||||
* | Enable noUnusedParameters option for vscode extension | Tetsuharu OHZEKI | 2019-12-11 | 5 | -5/+8 |
| | |||||
* | Use ES2018 for vscode extension | Tetsuharu OHZEKI | 2019-12-11 | 1 | -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 commas | Laurențiu Nicola | 2019-12-09 | 31 | -232/+233 |
| | |||||
* | Allow disabling sysroot | Aleksey Kladov | 2019-12-09 | 2 | -1/+7 |
| | | | | Might be helpful for debugging | ||||
* | Add rollup sourcemap and fix launch.json | Edwin Cheng | 2019-12-08 | 3 | -0/+57 |
| | |||||
* | Merge #2508 | bors[bot] | 2019-12-08 | 1 | -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 Windows | Laurențiu Nicola | 2019-12-08 | 1 | -5/+9 |
| | | |||||
* | | Code: bump deps | Laurențiu Nicola | 2019-12-08 | 4 | -418/+253 |
|/ | |||||
* | Code: check whether the LSP binary is in PATH | Laurențiu Nicola | 2019-12-08 | 4 | -6/+23 |
| | |||||
* | Fix npm vulnerability warning | Edwin Cheng | 2019-12-06 | 1 | -3/+3 |
| | |||||
* | rename ra_ide_api -> ra_ide | Aleksey Kladov | 2019-11-27 | 1 | -0/+0 |
| | |||||
* | Add rust-analyzer-expand-macro function for Emacs | Florian Diebold | 2019-11-20 | 1 | -0/+28 |
| | |||||
* | Merge pull request #2297 from kiljacken/master | Aleksey Kladov | 2019-11-20 | 2 | -13/+2 |
|\ | | | | | Add fancy truncation of type hints. | ||||
| * | Move type inlay hint truncation to language server | Emil Lauridsen | 2019-11-19 | 2 | -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 formating | Edwin Cheng | 2019-11-19 | 1 | -1/+1 |
| | | |||||
* | | Use DocumentProvider instead of Hover | Edwin Cheng | 2019-11-19 | 3 | -33/+75 |
| | | |||||
* | | Change return type of expand_macro | Edwin Cheng | 2019-11-19 | 1 | -5/+8 |
| | | |||||
* | | Fix npm formatting | Edwin Cheng | 2019-11-19 | 2 | -14/+14 |
| | | |||||
* | | Add recursive expand in vscode | Edwin Cheng | 2019-11-19 | 3 | -5/+62 |
|/ | |||||
* | Fix format | oxalica | 2019-11-16 | 1 | -1/+3 |
| | |||||
* | Check exit code of `cargo watch` | oxalica | 2019-11-15 | 1 | -3/+3 |
| | |||||
* | Handle errors when `cargo watch` fails | oxalica | 2019-11-15 | 1 | -0/+5 |
| | |||||
* | Add link to the vscode VIM extension compatibility warning. | krk | 2019-10-30 | 1 | -1/+1 |
| | |||||
* | document feature flags | Aleksey Kladov | 2019-10-25 | 3 | -14/+0 |
| | |||||
* | Merge #1980 | bors[bot] | 2019-10-23 | 3 | -1/+28 |
|\ | | | | | | | | | | | | | | | 1980: Shorten inline type hints r=matklad a=detrumi Implements #1946 Co-authored-by: Wilco Kusee <[email protected]> | ||||
| * | Do not truncate the range | Wilco Kusee | 2019-10-23 | 1 | -30/+10 |
| | | |||||
| * | Make inlay hint length configurable | Wilco Kusee | 2019-10-18 | 3 | -14/+37 |
| | | |||||
| * | Truncate hints longer than 20 characters | Wilco Kusee | 2019-10-10 | 1 | -4/+28 |
| | | |||||
* | | Adds config option for cargo-watch `--ignore` flag | Roberto Vidal | 2019-10-17 | 3 | -2/+21 |
| | | |||||
* | | Add rust-analyzer.showWorkspaceLoadedNotification to package.json | Laurențiu Nicola | 2019-10-17 | 1 | -0/+5 |
| | | |||||
* | | Merge #1984 | bors[bot] | 2019-10-10 | 2 | -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 vsce | kjeremy | 2019-10-10 | 2 | -29/+21 |
| |/ | |||||
* / | engine.vscode and @types/vscode should match | kjeremy | 2019-10-10 | 1 | -1/+1 |
|/ | |||||
* | Fix | arsdragonfly | 2019-09-28 | 1 | -3/+1 |
| | |||||
* | Fix tests | arsdragonfly | 2019-09-27 | 2 | -6/+5 |
| |