Ross Anderson

Hi @johndog , thanks for the report. I'm happy to facilitate contributions and deployments but I'm no longer actively doing bug fixes or feature work on these extensions. I don't...

This sounds like a great idea. Maybe you could optionally declare one as the default too. My only concern is to be sure that no secrets are stored in plaintext...

Hi @le0li9ht , thanks for the report. I'm not actively maintaining this repo aside from facilitating contributions. If you're interested, the last contributor wrote some great instructions here on how...

Thanks for the report! What version of the extension do you see this issue on? In latest I do see the take_any keyword defined in the tmlanguage syntax https://github.com/rosshamish/kuskus/blob/master/kusto-syntax-highlighting/syntaxes/kusto.tmLanguage.yml#L108 If...

hi @johndog , thanks for the report. I'm not actively maintaining this extension anymore but I'm open to facilitating contributions. I see a similar report at #102 , probably related.

Sure! Do you know what's involved in publishing an extension to Azure Data Studio? Is it the same format? Contributions are welcome on this.

Looks like Data Studio uses a different publishing mechanism than VS Code. But, the packaging works the same (uses `vsce` to create a .vsix file). Instead of publishing to the...

This will reduce the install time of the language server. Right now it's 1-5 minutes and sometimes (?) requires a restart of vs code. If it is webpack bundled, it...

This is already partially done, but not exposed in the extension. Good contribution opportunity

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...