Run query from selection / from document

[rosshamish]

We don't want to dupe functionality from Kusto Explorer / Kusto Web Explorer though, so probably the best route here is to generate a link to kusto web explorer with the query text url encoded, then use open() to open it in the browser. Shell out to web explorer, which already implements all this. Folks can bounce back and forth between the web explorer (for execution) and vs code (for source control).

Best part of this would be that the web explorer and vs code's editor capabilities are based on the same npm module(s), so the editing experience should/would be exactly the same. Consistency!

[stevenhurwitt]

Why do you not want to duplicate functionality here? Personally I've been looking for a way to query Kusto Explorer from either Visual Studio or Visual Studio Code - since I can also query SQL Server from both of these. I think it'd be really cool to extend the Language Server you've already made into a view of databases/tables and a way to execute queries from .kql scripts. Something like https://github.com/Microsoft/vscode-mssql. Might look into this but I'm not too knowledgeable on the matter...

[rosshamish]

The motivation for not duplicating functionality was to avoid duplicating the work. For our use case (the group of us that originally worked on this), we were totally content with using kusto's web explorer as the execution environment.

However, as I mentioned in my reply to #26, if you're interested in extending this project to support an execution environment, you're more than welcome. Probably the best route would be to work in your fork, and periodically send PRs back here, and we can work together on reviewing/testing and then publishing the changes to the extension store. I don't check github notifications much but I do check email, so feel free to send me a line there.

[stevenhurwitt]

thanks, sounds good man!