rust-analyzer - [FORK] modified to work on wasm targets

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use named multiline Problem Matcher	kjeremy	2019-02-18	1	-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
*	Specify vscode 1.31	kjeremy	2019-02-12	1	-1/+1
\|
*	Update dependencies	DJMcNab	2019-02-10	1	-2/+2
\|
*	Add support for a seperate output channel for trace messages	DJMcNab	2019-02-10	1	-1/+1
\|
*	Update npm packages	kjeremy	2019-02-07	1	-7/+7
\|
*	Add new configuration "enableEnhancedTyping" to control registering of ↵	Ville Penttinen	2019-02-07	1	-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.
*	Add category to the commands	DJMcNab	2019-01-29	1	-8/+16
\|
*	Start the extension when rust-analyzer status is run	DJMcNab	2019-01-29	1	-1/+3
\|
*	align command naming	Aleksey Kladov	2019-01-28	1	-25/+25
\|
*	add gc request	Aleksey Kladov	2019-01-25	1	-0/+4
\|
*	ad status command	Aleksey Kladov	2019-01-22	1	-0/+4
\|
*	Fail Travis on Prettier formatting issue	Alan Du	2019-01-15	1	-1/+1
\|
*	:arrow_up: npm	Aleksey Kladov	2019-01-13	1	-3/+3
\|
*	Allow user to set path to ra_lsp_server in vscode settings	gentoo90	2019-01-05	1	-0/+7
\|
*	index stuff produced by macros	Aleksey Kladov	2019-01-03	1	-1/+1
\|
*	named multiline problem patterns are not parsed properly in vscode at the moment	Bernardo	2019-01-01	1	-2/+29
\|
*	fix regex and add rustc-watch problem matcher	Bernardo	2019-01-01	1	-23/+32
\|
*	Support tracing lsp requests.	DJMcNab	2018-12-20	1	-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
*	use new clear-terminal feature	Aleksey Kladov	2018-12-15	1	-2/+2
\|
*	remove direct dep on event-stream: malisious version was unpublished	Aleksey Kladov	2018-12-09	1	-1/+0
\|
*	Add package command and upgrade event-stream	DJMcNab	2018-12-08	1	-1/+2
\|
*	Run npm update and add private and preview flags	DJMcNab	2018-12-08	1	-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
*	Improve the extend keybinding to not conflict	DJMcNab	2018-12-08	1	-1/+1
\|
*	fix npm problems	Aleksey Kladov	2018-11-27	1	-0/+1
\|
*	Update vscode-languageclient package to support RenameOptions	Jeremy A. Kolb	2018-10-19	1	-2/+2
\|
*	Format vscode extension and add npm run fix	Adolfo Ochagavía	2018-10-09	1	-0/+1
\|
*	Run prettier on all files	Daniel McNab	2018-10-08	1	-1/+2
\|
*	Add tslint and prettier to ci	Daniel McNab	2018-10-08	1	-5/+14
\|
*	Dynamically apply highlightingOn config	Adolfo Ochagavía	2018-10-06	1	-1/+1
\| \| \| \|	Fixes #84
*	Add a setting to disable custom syntax highlighting	Adolfo Ochagavía	2018-09-29	1	-0/+11
\|
*	Remove undefined command	ekrctb	2018-09-21	1	-4/+0
\|
*	rename all things	Aleksey Kladov	2018-09-16	1	-0/+149