about summary refs log tree commit diff
path: root/editors/code/package.json
AgeCommit message (Collapse)AuthorLines
2019-03-03Add vscode support for range in SyntaxTreeParamsVille Penttinen-1/+1
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.
2019-02-26Change default value of highlightingOn to falseVille Penttinen-1/+1
2019-02-18Use named multiline Problem Matcherkjeremy-29/+2
Now that https://github.com/Microsoft/vscode/pull/65840 is in the latest release we can use the first commit from https://github.com/rust-analyzer/rust-analyzer/pull/408
2019-02-12Specify vscode 1.31kjeremy-1/+1
2019-02-10Update dependenciesDJMcNab-2/+2
2019-02-10Add support for a seperate output channel for trace messagesDJMcNab-1/+1
2019-02-07Update npm packageskjeremy-7/+7
2019-02-07Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen-0/+5
"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.
2019-01-29Add category to the commandsDJMcNab-8/+16
2019-01-29Start the extension when rust-analyzer status is runDJMcNab-1/+3
2019-01-28align command namingAleksey Kladov-25/+25
2019-01-25add gc requestAleksey Kladov-0/+4
2019-01-23ad status commandAleksey Kladov-0/+4
2019-01-15Fail Travis on Prettier formatting issueAlan Du-1/+1
2019-01-13:arrow_up: npmAleksey Kladov-3/+3
2019-01-05Allow user to set path to ra_lsp_server in vscode settingsgentoo90-0/+7
2019-01-03index stuff produced by macrosAleksey Kladov-1/+1
2019-01-01named multiline problem patterns are not parsed properly in vscode at the momentBernardo-2/+29
2019-01-01fix regex and add rustc-watch problem matcherBernardo-23/+32
2018-12-20Support tracing lsp requests.DJMcNab-0/+11
TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway
2018-12-15use new clear-terminal featureAleksey Kladov-2/+2
2018-12-09remove direct dep on event-stream: malisious version was unpublishedAleksey Kladov-1/+0
2018-12-08Add package command and upgrade event-streamDJMcNab-1/+2
2018-12-08Run npm update and add private and preview flagsDJMcNab-7/+9
Private stops npm publish working, which would be nonsensical anyway In case it gets added to the vscode extension repository, preview marks it as such Private may also prevent publishing to the vscode extension repository
2018-12-08Improve the extend keybinding to not conflictDJMcNab-1/+1
2018-11-27fix npm problemsAleksey Kladov-0/+1
2018-10-19Update vscode-languageclient package to support RenameOptionsJeremy A. Kolb-2/+2
2018-10-09Format vscode extension and add npm run fixAdolfo Ochagavía-0/+1
2018-10-08Run prettier on all filesDaniel McNab-1/+2
2018-10-08Add tslint and prettier to ciDaniel McNab-5/+14
2018-10-06Dynamically apply highlightingOn configAdolfo Ochagavía-1/+1
Fixes #84
2018-09-29Add a setting to disable custom syntax highlightingAdolfo Ochagavía-0/+11
2018-09-21Remove undefined commandekrctb-4/+0
2018-09-16rename all thingsAleksey Kladov-0/+149