aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
...
* | Remove unnecessary async from vscode language client creationveetaha2020-04-252-2/+2
|/
*-. Merge #3998 #4006bors[bot]2020-04-241-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 <[email protected]> Co-authored-by: Leander Tentrup <[email protected]> Co-authored-by: Leander Tentrup <[email protected]>
| * | Jump to sourceChanges in other filesTimo Freiberg2020-04-211-3/+5
| | |
* | | Disable onEnter command by defaultAleksey Kladov2020-04-231-5/+0
| | | | | | | | | | | | | | | We are transitioning from experimental to production-ready stance, so it makes sense to disable potentially disruptive features by default.
* | | tasks.json SupportJonathan Dickinson2020-04-231-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.
* | | Merge #4090bors[bot]2020-04-221-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4090: Fix config naming r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Align the name of proc-macro enabling flagAleksey Kladov2020-04-221-1/+1
| |/ / | | | | | | | | | We use `enable`, not `enabled` elsewhere
* | | npm updatekjeremy2020-04-222-50/+109
| | |
* | | Merge #4081bors[bot]2020-04-221-2/+35
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4081: Work around crlf in syntax tree r=matklad a=Veetaha Workarounds fixes #4067 Co-authored-by: veetaha <[email protected]>
| * | | Refactor the workaround a bitveetaha2020-04-221-19/+16
| | | |
| * | | Work around crlf in syntax treeveetaha2020-04-221-2/+38
| |/ /
* / / Fix .rast tmGrammar to account for numbers in identifiersveetaha2020-04-221-1/+1
|/ /
* / Add semantic tag for unresolved referencesAleksey Kladov2020-04-181-0/+4
|/ | | | | | | | | | | This is a quick way to implement unresolved reference diagnostics. For example, adding to VS Code config "editor.tokenColorCustomizationsExperimental": { "unresolvedReference": "#FF0000" }, will highlight all unresolved refs in red.
* Add proc-macro cli command for rust-analyzerEdwin Cheng2020-04-161-5/+0
|
* Add config for proc_macroEdwin Cheng2020-04-162-0/+11
|
* Merge #3948bors[bot]2020-04-161-2/+3
|\ | | | | | | | | | | | | | | | | | | | | 3948: fix: inlay hints config desyncronization between the frontend and the backend r=matklad a=Veetaha See the explanation in the issue comment: https://github.com/rust-analyzer/rust-analyzer/issues/3924#issuecomment-612444566 Workaround-ly fixes: #3924 Co-authored-by: veetaha <[email protected]>
| * fix: inlay hints config desyncronization between the frontend and the backendveetaha2020-04-111-2/+3
| | | | | | | | | | See the explanation in the issue comment: https://github.com/rust-analyzer/rust-analyzer/issues/3924#issuecomment-612444566
* | Merge #3962bors[bot]2020-04-151-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 3962: Fix parentModule shortcut conflict r=matklad a=CodeSandwich The default parentModule shortcut conflicts with VSCode's built-in undo selection Co-authored-by: Igor Å»uk <[email protected]>
| * | Fix parentModule shortcut conflictIgor Żuk2020-04-131-1/+1
| |/ | | | | The default parentModule shortcut conflicts with VSCode's built-in undo selection
* / Bump @types/vscode and vscode-languageclientkjeremy2020-04-142-20/+20
|/
* Merge #3942bors[bot]2020-04-111-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 <[email protected]>
| * vscode: fix typing bug in configveetaha2020-04-111-9/+30
| |
* | vscode: fix indentveetaha2020-04-111-5/+5
|/
* Enable the SemanticTokensFeature by defaultkjeremy2020-04-084-18/+8
| | | | | | | 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
* Update some packageskjeremy2020-04-072-25/+25
|
* Better config scheme & defaultsAleksey Kladov2020-04-071-6/+14
|
* Merge pull request #3853 from matklad/cfAleksey Kladov2020-04-061-4/+1
|\ | | | | Make control token modifier less ambiguous
| * Make control token modifier less ambiguousAleksey Kladov2020-04-061-4/+1
| | | | | | | | | | | | | | | | | | In textmate, keyword.control is used for all kinds of things; in fact, the default scope mapping for keyword is keyword.control! So let's add a less ambiguous controlFlow modifier See Microsoft/vscode#94367
* | Merge #3844bors[bot]2020-04-041-0/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3844: vscode: restore removed default values r=matklad a=Veetaha After refactoring the config we forgot to set defaults for some properties like workspaceLoaded, callInfo.full, etc. This commit restored them to being turned on by defult, as well added defaults for other props to be more explicit on their defualt value. cc @matklad Co-authored-by: veetaha <[email protected]>
| * | vscode: restore removed default valuesveetaha2020-04-041-0/+5
| |/ | | | | | | | | | | | | | | After refactoring the config we forgot to set defaults for some properties like workspaceLoaded, callInfo.full, etc. This commit restored them to being turned on by defult, as well added defaults for other props to be more explicit on their defualt value.
* / vscode: log server binary pathveetaha2020-04-041-0/+2
|/
* Include grammar for syntax trees into vsixAleksey Kladov2020-04-031-0/+1
|
* Set semantic tokens supertypesAleksey Kladov2020-04-031-3/+6
|
* Bumps vsce to 1.75kjeremy2020-04-022-16/+24
| | | | Fixes a security vulnerability
* Fix semantic coloringAleksey Kladov2020-04-021-58/+27
|
* better wordingAleksey Kladov2020-04-021-1/+1
|
* Allow fully overriding check and fmt commandsAleksey Kladov2020-04-021-0/+14
|
* Remove vscode_lldb settingAleksey Kladov2020-04-021-0/+4
|
* Lean onto default implementation of configsAleksey Kladov2020-04-025-59/+8
|
* New config in package.jsonAleksey Kladov2020-04-021-120/+125
|
* vscode: postrefactorveetaha2020-04-021-12/+6
|
* vscode: postrefactor variable namesveetaha2020-04-021-8/+8
|
* vscode: add goto definition from rust file to syntax tree editorveetaha2020-04-021-5/+83
|
* Merge #3820bors[bot]2020-04-025-272/+0
|\ | | | | | | | | | | | | | | | | | | | | 3820: Remove old syntax highlighting r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Remove old syntax highlightingAleksey Kladov2020-04-025-272/+0
| |
* | Merge #3817bors[bot]2020-04-023-1/+50
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <[email protected]>
| * | vscode: add highlighting of syntax treeveetaha2020-04-023-1/+50
| |/
* / vscode: add support for light themes and color customization for syntax tree ↵veetaha2020-04-012-2/+13
|/ | | | highlights
* rollup 2.3.2kjeremy2020-04-012-4/+4
|
*-. Merge #3780 #3787bors[bot]2020-03-312-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 <[email protected]> Co-authored-by: Veetaha <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 13:02:32 +0000