| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Refactor the workaround a bit | veetaha | 2020-04-22 | 1 | -19/+16 |
| | | |||||
| * | Work around crlf in syntax tree | veetaha | 2020-04-22 | 1 | -2/+38 |
| | | |||||
| * | Remove vscode_lldb setting | Aleksey Kladov | 2020-04-02 | 1 | -0/+4 |
| | | |||||
| * | vscode: postrefactor | veetaha | 2020-04-02 | 1 | -12/+6 |
| | | |||||
| * | vscode: postrefactor variable names | veetaha | 2020-04-02 | 1 | -8/+8 |
| | | |||||
| * | vscode: add goto definition from rust file to syntax tree editor | veetaha | 2020-04-02 | 1 | -5/+83 |
| | | |||||
| * | Merge #3817 | bors[bot] | 2020-04-02 | 1 | -1/+4 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3817: vscode: highlight syntax tree ro editor r=matklad a=Veetaha Small textmate grammar declaration to make rust-analyzer syntax tree more easily inspectable: Btw, if we change the file extension of our `ra_syntax/test_data/**` files to `.rast` they should be highlighted in vscode too. The colors of the tokens are actually going to be color-theme dependent, or you can customize them via: ```jsonc { "editor.tokenColorCustomizations": { "textMateRules": [ { "scope": "name", "settings": { /* */ } } ] } } ```  Related: #3682 Co-authored-by: veetaha <[email protected]> | ||||
| | * | vscode: add highlighting of syntax tree | veetaha | 2020-04-02 | 1 | -1/+4 |
| | | | |||||
| * | | vscode: add support for light themes and color customization for syntax tree ↵ | veetaha | 2020-04-01 | 1 | -2/+4 |
| |/ | | | | highlights | ||||
| * | vscode: small refactor | veetaha | 2020-03-31 | 1 | -1/+1 |
| |\ | |||||
| | * | vscode: apply review nits | Veetaha | 2020-03-31 | 1 | -1/+1 |
| | | | |||||
| * | | vscode: scroll to the syntax node in rust editor when highlighting | veetaha | 2020-03-31 | 1 | -1/+2 |
| |/ | |||||
| * | vscode: use ctx.subscriptions instead of local .disposables | veetaha | 2020-03-31 | 1 | -15/+12 |
| | | |||||
| * | vscode: add syntax tree inspection hovers and highlights | veetaha | 2020-03-31 | 1 | -53/+116 |
| | | |||||
| * | vscode: fix release tag retrieval | Veetaha | 2020-03-27 | 1 | -1/+1 |
| | | | | Co-Authored-By: Laurențiu Nicola <[email protected]> | ||||
| * | vscode: show release tag with along with the commit hash for RA version command | veetaha | 2020-03-26 | 1 | -2/+7 |
| | | |||||
| * | vscode: refactor analyzer status | veetaha | 2020-03-25 | 1 | -20/+11 |
| | | |||||
| * | Rewrite auto-update | Aleksey Kladov | 2020-03-19 | 1 | -13/+3 |
| | | | | | | | | | | | | | | | Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server). | ||||
| * | Separate persistent mutable state from config | Aleksey Kladov | 2020-03-16 | 1 | -1/+1 |
| | | | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent. | ||||
| * | Merge #3534 | bors[bot] | 2020-03-16 | 1 | -2/+1 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3534: Feature: vscode impl nightlies download and installation r=Veetaha a=Veetaha I need to test things more, but the core shape of the code is quite well-formed. The main problem is that we save the release date only for nightlies and there are no means to get the release date of the stable extension (i.e. for this we would need to consult the github releases via a network request, or we would need to somehow save this info into package.json or any other file accessible from the extension code during the deployment step, but this will be very hard I guess). So there is an invariant that the users can install nightly only from our extension and they can't do it manually, because when installing the nightly `.vsix` we actually save its release date to `globalState` Closes: #3402 TODO: - [x] More manual tests and documentation cc @matklad @lnicola Co-authored-by: Veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]> | ||||
| | * | vscode: amend server installation logic to account for nightlies | Veetaha | 2020-03-14 | 1 | -2/+1 |
| | | | |||||
| * | | Merge #3540 | bors[bot] | 2020-03-16 | 1 | -7/+9 |
| |\ \ | | | | | | | | | | | | | | | | | | | | | | 3540: Swtches to rust SSR query check r=matklad a=mikhail-m1 related to #3186 Co-authored-by: Mikhail Modin <[email protected]> | ||||
| | * | | Swtches to rust SSR query check | Mikhail Modin | 2020-03-15 | 1 | -7/+9 |
| | |/ | |||||
| * | | fixup! feat: add debug code lens | Hannes De Valkeneer | 2020-03-12 | 1 | -6/+1 |
| | | | | | | | | | avoid repetition of `--no-run` | ||||
| * | | fixup! feat: add debug code lens | Hannes De Valkeneer | 2020-03-12 | 1 | -2/+1 |
| | | | |||||
| * | | feat: add debug code lens | Hannes De Valkeneer | 2020-03-11 | 1 | -1/+27 |
| |/ | | | | Refs #3539 | ||||
| * | Centralize the check for languageId on document | Julien Roncaglia | 2020-03-02 | 1 | -2/+3 |
| | | | | | Also move visibleRustEditors to Ctx | ||||
| * | vscode: run fmt | Veetaha | 2020-02-24 | 1 | -1/+1 |
| | | |||||
| * | vscode: migrate syntax_tree to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -20/+7 |
| | | |||||
| * | vscode: migrate ssr to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -11/+5 |
| | | |||||
| * | vscode: migrate runnables to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -22/+7 |
| | | |||||
| * | vscode: migrate parent_module to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -7/+3 |
| | | |||||
| * | vscode: migrate on_enter to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -14/+7 |
| | | |||||
| * | vscode: migrate matching_brace to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -12/+3 |
| | | |||||
| * | vscode: migrate join_lines to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -13/+4 |
| | | |||||
| * | vscode: migrate collectGarbage to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -5/+4 |
| | | |||||
| * | vscode: migrate expand_macro to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -13/+5 |
| | | |||||
| * | vscode: migrate analyzer_status to rust-analyzer-api.ts | Veetaha | 2020-02-24 | 1 | -4/+2 |
| | | |||||
| * | Don't block onEnter if request fails | Aleksey Kladov | 2020-02-24 | 1 | -0/+6 |
| | | | | | closes #3286 | ||||
| * | Use stdout directly | Edwin Cheng | 2020-02-21 | 1 | -2/+1 |
| | | |||||
| * | Use ensureServerBinary instead | Edwin Cheng | 2020-02-21 | 1 | -5/+17 |
| | | |||||
| * | Add trailing newline | Edwin Cheng | 2020-02-21 | 1 | -1/+2 |
| | | |||||
| * | Improve server version info | Edwin Cheng | 2020-02-21 | 2 | -0/+10 |
| | | |||||
| * | enforce camel case | Aleksey Kladov | 2020-02-21 | 1 | -2/+2 |
| | | |||||
| * | vscode: press ; to respect semicolons | Veetaha | 2020-02-17 | 2 | -3/+3 |
| | | |||||
| * | Simplify some more ctors | Aleksey Kladov | 2020-02-17 | 3 | -9/+3 |
| | | |||||
| * | Simplify TS reload logic | Aleksey Kladov | 2020-02-17 | 1 | -7/+0 |
| | | | | | Fixes #3164 | ||||
| * | Init implementation of structural search replace | Mikhail Modin | 2020-02-14 | 2 | -0/+37 |
| | | |||||
| * | Merge #3024 | bors[bot] | 2020-02-05 | 2 | -1/+3 |
| |\ | | | | | | | | | | | | | | | 3024: vscode: eliminate floating promises and insane amount of resource handle leaks r=matklad a=Veetaha Khm, yeah ... Co-authored-by: Veetaha <[email protected]> | ||||
| | * | vscode: eliminate floating promises and insane amount of resource handle leaks | Veetaha | 2020-02-05 | 2 | -1/+3 |
| | | | |||||
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |