Control Log json communications with vscode-client tooling

[albfan]

Allow to control wheter or not you want to see the json messages between client and server

NOTE: I set the client id as vala (vala.trace.server), but there're other settings using vls as id (vls.execPath).

fixes #6

[albfan]

There's a simplest version for the property editable on settings tab which is:

				"vala.trace.server": {
					"scope": "window",
					"type": "string",
					"enum": [
						"off",
						"messages",
						"verbose"
					],
					"default": "off",
					"description": "Traces the communication between VS Code and the language server."
				}

But I put the full featured one (which allows to decide on format (text or json) for output. Is a little worse because you have to edit directly on settings.json. I don't have a preference if this seems interesting

[Prince781]

Good commit, but you should bump the version number up to 1.0.3 for this

[Prince781]

I tried this out but it doesn't seem to affect anything. Could you explain how this feature is used and what should change in the output of the extension?

[albfan]

I think you need to remove installed plugin to see it work.

Will change the version in a while

To use you press Ctrl+, and change the setting for vala.trace.server.

So you can enable for a while, and disable in same session.

Attached screencast (NOTE: gitlab render webm by default)Uploading vls-json-log.zip…

This allows to remove G_MESSAGE_DEBUG or add a new true/false property trace.server.app or similar that adds the G_MESSAGE_DEBUG= so you can control if server logs its output or not, etc...

[Prince781]

@albfan There's no attachment. You can use something like https://streamable.com if you want to upload screencasts

[benwaffle]

if you're changing the prefix can you change vls.languageServerPath to vala.languageServerPath