aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Add showWorkspaceLoadedNotification to vscode clientVille Penttinen2019-03-062-1/+10
| | | | | | | | | This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent.
* Allow syntax tree to update when changing filesVille Penttinen2019-03-032-17/+26
| | | | | | 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-033-13/+11
|
* Add vscode support for range in SyntaxTreeParamsVille Penttinen2019-03-032-10/+40
| | | | | | 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.
* Fix trace and prettierDJMcNab2019-02-101-2/+4
|
* Add support for a seperate output channel for trace messagesDJMcNab2019-02-101-2/+5
|
* Run prettierVille Penttinen2019-02-071-4/+11
|
* Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen2019-02-072-1/+28
| | | | | | | | | | | | | | | | | | "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
|
* Clear the console when running single taskskjeremy2019-01-301-1/+2
|
* align command namingAleksey Kladov2019-01-2812-30/+47
|
* add gc requestAleksey Kladov2019-01-251-0/+3
|
* better statsAleksey Kladov2019-01-252-7/+59
|
* ad status commandAleksey Kladov2019-01-223-0/+15
|
* Config for raLspServerPath will be overwritten if __RA_LSP_SERVER_DEBUG is setAndrew Ross2019-01-191-2/+5
| | | | | | | Changed presentation from clear to reveal silent Removed the vscode gitignore entry Added debugging documentation Added tasks and launch configs
* Prettier fixAlan Du2019-01-151-1/+4
|
* Reveal the newly added source change in the editor.Jeremy A. Kolb2019-01-141-0/+1
|
* npm fix runJeremy Kolb2019-01-124-9/+16
|
* Move run_single into runnablesJeremy Kolb2019-01-124-66/+17
|
* Code lens support for running testsJeremy A. Kolb2019-01-113-0/+68
|
* Allow user to set path to ra_lsp_server in vscode settingsgentoo902019-01-052-1/+6
|
* fix open of created or renamed fileBernardo2019-01-051-1/+2
|
* use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo2019-01-031-33/+10
|
* highlight macro identsAleksey Kladov2018-12-281-1/+2
|
* Merge #302bors[bot]2018-12-241-1/+25
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 302: WIP: Support tracing lsp requests. r=DJMcNab a=DJMcNab EDIT: We need to work out a better way to handle settings before this can be merged. Help wanted TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway. (Continuation of #84 [#99 only disabled using it, not making sure we don't send it]). These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/ Co-authored-by: DJMcNab <[email protected]>
| * Add a very hacky workaround to not trace decorations requestsDJMcNab2018-12-241-1/+25
| |
* | Fix analyzer extension fail when there are enabled any VIM extension.frai2018-12-221-13/+17
|/
* use new clear-terminal featureAleksey Kladov2018-12-151-2/+2
|
* Remove uneeded charactersDJMcNab2018-12-081-3/+3
|
* Fix on enterAdolfo Ochagavía2018-11-091-2/+2
|
* workspace-symbols function for EmacsAleksey Kladov2018-11-081-1/+4
|
* Rename File -> SourceFileNodeAleksey Kladov2018-11-071-2/+2
|
* Fully add inline modules to module treeAleksey Kladov2018-11-052-9/+8
|
* Fix typoPascal Hertleif2018-10-211-1/+1
| | | Truly an A+, errrr, +a commit
* Fold multiline commentsAdolfo Ochagavía2018-10-121-2/+2
|
* Remove error publishing through publishDecorationsAdolfo Ochagavía2018-10-101-7/+0
|
* Format vscode extension and add npm run fixAdolfo Ochagavía2018-10-093-14/+28
|
* Add on-enter handlerAleksey Kladov2018-10-093-2/+51
| | | | Now, typing doc comments is much more pleasant
* Run prettier on all filesDaniel McNab2018-10-0817-102/+203
|
* Add tslint and prettier to ciDaniel McNab2018-10-081-13/+13
|
* Add some commentsAdolfo Ochagavía2018-10-084-25/+44
|
* Fix remaining tslint suggestionsAdolfo Ochagavía2018-10-0814-77/+81
|
* Apply tslint suggestions, round oneAdolfo Ochagavía2018-10-0715-242/+245
|
* Refactor vscode extensionAdolfo Ochagavía2018-10-0714-415/+518
|
* 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-12-13 15:52:47 +0000