aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/extension.ts
Commit message (Collapse)AuthorAgeFilesLines
* switch to official extend selection APIAleksey Kladov2019-04-211-4/+0
|
* start cargo watch if not started interactivelyBernardo2019-04-191-1/+8
|
* cargo watch start and stop commandsBernardo2019-04-191-1/+15
|
* PrettierRoberto Vidal2019-04-161-2/+1
|
* Adds "restart server" commandRoberto Vidal2019-04-161-1/+15
|
* Fix prettier errorEdwin Cheng2019-04-021-1/+1
|
* Improve cargo-watch usageEdwin Cheng2019-04-021-2/+2
|
* Separate out the interactive cargo watch procedureIgor Matuszewski2019-03-181-63/+3
|
* Reformat using PrettierIgor Matuszewski2019-03-181-12/+30
|
* Remove unused importsIgor Matuszewski2019-03-181-2/+1
|
* Prefer installing `cargo-watch` via Task APIIgor Matuszewski2019-03-181-23/+14
| | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors.
* Ask the user to install and start cargo watchIgor Matuszewski2019-03-181-5/+61
|
* Allow syntax tree to update when changing filesVille Penttinen2019-03-031-2/+2
| | | | | | Previously when using the file based syntax tree, it would not update until a change had been made in the new file. Now we automatically update the syntax tree to match the current file.
* Rename syntaxtree text provider to SyntaxTreeContentProviderVille Penttinen2019-03-031-5/+5
|
* Add vscode support for range in SyntaxTreeParamsVille Penttinen2019-03-031-1/+5
| | | | | | This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range.
* Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen2019-02-071-1/+3
| | | | | | | | | | | | | | | | | | "type" command This further fixes problems when having a VIM extension (at least vscodevim) enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when enableEnhancedTyping is set to `false`. The problem is dependent on the order in which extensions are activated, if rust-analyzer is activated before `vscodevim`, rust-analyzer will register the `type` command, and when `vscodevim` finally attempts to activate, it will fail to register the command. This causes `vscodevim` to stop working properly. This setting allows users to disable the registerCommand `type` in rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`. Currently changing the setting requires reloading of the window.
* Implement lens for impls and support resolving lenses.Jeremy Kolb2019-02-041-0/+12
|
* align command namingAleksey Kladov2019-01-281-15/+25
|
* add gc requestAleksey Kladov2019-01-251-0/+3
|
* better statsAleksey Kladov2019-01-251-1/+4
|
* ad status commandAleksey Kladov2019-01-221-0/+1
|
* npm fix runJeremy Kolb2019-01-121-2/+4
|
* Move run_single into runnablesJeremy Kolb2019-01-121-1/+1
|
* Code lens support for running testsJeremy A. Kolb2019-01-111-0/+3
|
* Fix analyzer extension fail when there are enabled any VIM extension.frai2018-12-221-13/+17
|
* Fold multiline commentsAdolfo Ochagavía2018-10-121-2/+2
|
* Format vscode extension and add npm run fixAdolfo Ochagavía2018-10-091-8/+13
|
* Add on-enter handlerAleksey Kladov2018-10-091-1/+19
| | | | Now, typing doc comments is much more pleasant
* Run prettier on all filesDaniel McNab2018-10-081-10/+18
|
* Add some commentsAdolfo Ochagavía2018-10-081-3/+14
|
* Apply tslint suggestions, round oneAdolfo Ochagavía2018-10-071-11/+11
|
* Refactor vscode extensionAdolfo Ochagavía2018-10-071-415/+26
|
* Dynamically apply highlightingOn configAdolfo Ochagavía2018-10-061-11/+36
| | | | Fixes #84
* Add a setting to disable custom syntax highlightingAdolfo Ochagavía2018-09-291-4/+12
|
* goto super places cursor on modAleksey Kladov2018-09-161-0/+1
|
* rename all thingsAleksey Kladov2018-09-161-0/+400
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 13:27:36 +0000