about summary refs log tree commit diff
path: root/editors/code/src
AgeCommit message (Collapse)AuthorLines
2020-04-25Merge #4145bors[bot]-29/+0
4145: Remove dead code r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
2020-04-25Remove dead codeAleksey Kladov-29/+0
2020-04-25Remove unnecessary async from vscode language client creationveetaha-2/+2
2020-04-24Merge #3998 #4006bors[bot]-3/+5
3998: Make add_function generate functions in other modules via qualified path r=matklad a=TimoFreiberg Additional feature for #3639 - [x] Add tests for paths with more segments - [x] Make generating the function in another file work - [x] Add `pub` or `pub(crate)` to the generated function if it's generated in a different module - [x] Make the assist jump to the edited file - [x] Enable file support in the `check_assist` helper 4006: Syntax highlighting for format strings r=matklad a=ltentrup I have an implementation for syntax highlighting for format string modifiers `{}`. The first commit refactors the changes in #3826 into a separate struct. The second commit implements the highlighting: first we check in a macro call whether the macro is a format macro from `std`. In this case, we remember the format string node. If we encounter this node during syntax highlighting, we check for the format modifiers `{}` using regular expressions. There are a few places which I am not quite sure: - Is the way I extract the macro names correct? - Is the `HighlightTag::Attribute` suitable for highlighting the `{}`? Let me know what you think, any feedback is welcome! Co-authored-by: Timo Freiberg <timo.freiberg@gmail.com> Co-authored-by: Leander Tentrup <leander.tentrup@gmail.com> Co-authored-by: Leander Tentrup <ltentrup@users.noreply.github.com>
2020-04-22tasks.json SupportJonathan Dickinson-36/+67
Move the task provider anonymous class into a real class, as this seems to be how Microsoft do this in their documentation. resolveTask is now implemented, which is used by VSCode to determine how to execute tasks that the user has defined in tasks.json.
2020-04-22Refactor the workaround a bitveetaha-19/+16
2020-04-22Work around crlf in syntax treeveetaha-2/+38
2020-04-21Jump to sourceChanges in other filesTimo Freiberg-3/+5
2020-04-16Add config for proc_macroEdwin Cheng-0/+1
2020-04-11fix: inlay hints config desyncronization between the frontend and the backendveetaha-2/+3
See the explanation in the issue comment: https://github.com/rust-analyzer/rust-analyzer/issues/3924#issuecomment-612444566
2020-04-11Merge #3942bors[bot]-9/+30
3942: vscode: fix typing bug in config r=matklad a=Veetaha I noticed that the type of nullable properties in config is actually non-nullable ![Screenshot from 2020-04-11 15-29-45](https://user-images.githubusercontent.com/36276403/79043702-6a686d80-7c09-11ea-9ae8-f1a777c7d0f2.png) Co-authored-by: veetaha <veetaha2@gmail.com>
2020-04-11vscode: fix typing bug in configveetaha-9/+30
2020-04-11vscode: fix indentveetaha-5/+5
2020-04-08Enable the SemanticTokensFeature by defaultkjeremy-12/+7
This is covered under vscode's "editor.semanticHighlighting.enabled" setting plus the user has to have a theme that has opted into highlighting. Bumps required vscode stable to 1.44
2020-04-04vscode: log server binary pathveetaha-0/+2
2020-04-02Remove vscode_lldb settingAleksey Kladov-0/+4
2020-04-02Lean onto default implementation of configsAleksey Kladov-54/+7
2020-04-02vscode: postrefactorveetaha-12/+6
2020-04-02vscode: postrefactor variable namesveetaha-8/+8
2020-04-02vscode: add goto definition from rust file to syntax tree editorveetaha-5/+83
2020-04-02Merge #3820bors[bot]-262/+0
3820: Remove old syntax highlighting r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
2020-04-02Remove old syntax highlightingAleksey Kladov-262/+0
2020-04-02Merge #3817bors[bot]-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": { /* */ } } ] } } ``` ![image](https://user-images.githubusercontent.com/36276403/78204947-99f9d600-74a3-11ea-8315-cb1c87810c7c.png) Related: #3682 Co-authored-by: veetaha <veetaha2@gmail.com>
2020-04-02vscode: add highlighting of syntax treeveetaha-1/+4
2020-04-02vscode: add support for light themes and color customization for syntax tree ↵veetaha-2/+4
highlights
2020-03-31Merge #3780 #3787bors[bot]-54/+115
3780: Simplify r=matklad a=Veetaha I absolutely love tha fact that removing `.clone()` simplifies the code comparing to other languages where it's actually the contrary (ahem ~~`std::move()`~~) 3787: vscode: add syntax tree inspection hovers and highlights r=matklad a=Veetaha ![inspect-tree](https://user-images.githubusercontent.com/36276403/78029767-c7426900-7369-11ea-9ed6-b8a0f8e05bac.gif) I implemented the reverse mapping (when you hover in the rust editor), but it seems overcomplicated, so I removed it Related #3682 Co-authored-by: veetaha <veetaha2@gmail.com> Co-authored-by: Veetaha <veetaha2@gmail.com>
2020-03-31vscode: small refactorveetaha-1/+1
2020-03-31vscode: scroll to the syntax node in rust editor when highlightingveetaha-1/+2
2020-03-31vscode: apply review nitsVeetaha-1/+1
2020-03-31vscode: use ctx.subscriptions instead of local .disposablesveetaha-15/+12
2020-03-31vscode: add syntax tree inspection hovers and highlightsveetaha-55/+118
2020-03-31Pass string instread of WorkspaceFolderTim-5/+5
2020-03-31Remove unnecessary null checkTim-3/+1
2020-03-31Throw error if no folder is openedTim-4/+9
2020-03-31Use namespace importTim-19/+11
2020-03-30Add basic task supportTim-6/+77
This adds basic support for running `cargo build`, `cargo run`, etc.
2020-03-30Code review fixesKirill Bulatov-6/+8
Co-Authored-By: Veetaha <veetaha2@gmail.com>
2020-03-30Style fixesKirill Bulatov-5/+7
2020-03-30Send the config from the clientKirill Bulatov-24/+28
2020-03-30Process configuration response draftKirill Bulatov-3/+3
2020-03-30Client side draftKirill Bulatov-0/+6
2020-03-27vscode: fix release tag retrievalVeetaha-1/+1
Co-Authored-By: Laurențiu Nicola <lnicola@users.noreply.github.com>
2020-03-27vscode: show release tag with along with the commit hash for RA version commandveetaha-2/+7
2020-03-26Merge #3725bors[bot]-23/+21
3725: vscode: fix local devel and remove disposables memory leak on server restrart r=matklad a=Veetaha Co-authored-by: veetaha <veetaha2@gmail.com>
2020-03-26vscode: small post-refactorveetaha-3/+1
2020-03-26vscode: fix memory leak on server restartveetaha-15/+13
The memory leak was because on the server restrart the array of extensionContext.substiptions was not cleared
2020-03-26vscode: fix local develveetaha-5/+7
The value of releaseTag is not undefined, but null in actual package.json
2020-03-26Merge #3726bors[bot]-20/+11
3726: vscode: refactor analyzer status r=matklad a=Veetaha Co-authored-by: veetaha <veetaha2@gmail.com>
2020-03-25vscode: refactor analyzer statusveetaha-20/+11
2020-03-25Use the right arch name for x86 (32 bit)Aleksey Kladov-1/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-16 03:43:18 +0000