@Jason Jones 
Our main VS Code extension provides a UI for debugging a REST service. It will prompt for data to create a REST request, makes the request, and attaches the debugger to the IRIS process that handles the request so you can step through the code like any other method.

@Kwabena Ayim-Aboagye No, there hasn't. Even if we had formatting for your specific example, the extra newlines would be erased when the document gets saved on the server. The only code in class definitions that's preserved as-is is implementation code enclosed in curly braces. The rest is stored in a global and regenerated from the global after a save.

@Yone Moreno 
Did you try $ZSTRIP with the following arguments?

Set string = $ZSTRIP(string,"<>",$CHAR(13,10))

$ZSTRIP without a mask code in the second argument and with specific characters as the third argument will strip just those specific characters.

@David Cui 
I can confirm that IRIS versions 2023.1.5, 2024.1.1 and 2024.2 will support this feature. It has not been released in the 2024.2 preview stream yet though, which is why the GitHub Pull Request that implements the VS Code-side work hasn't been merged.

@Mario Sanchez Macias 
Please see this page in our documentation for how to use a self-signed certificate.

I'm not familiar with all of the Zen specific methods in that class. For working with JSON outside the Zen framework though (for example, in REST APIs), new code should use Dynamic Objects.

@Alin Soare 
What "auto-formatting" are you referring to? Can you provide before and after screenshots showing what gets changed on save?

@Evgeniy Potapov You can use Dynamic Objects for working with JSON data

@Lukas Dolezal 
VS Code's View Other command supports jumping to the same line in the INT routine, but that support requires an InterSystems server with Atelier API version 4 or above (Cache 2018.1.6+, IRIS 2019.1.2+, 2020.1.1+, 2021.1+). If you're not using one of those versions then the location mapping won't work.

An important detail about the independent Studio is that it is installed in its own directory, so it won't be uninstalled when you upgrade/add/remove IRIS instances on your system. Also, since the 2024.1 Studio is forward-compatible, you won't need to update it every time a new IRIS version is released.

There is an open feature request for automatic indentation support, but that doesn't include adding newlines: https://github.com/intersystems/language-server/issues/293

You can use your second example above, then copy the content into a new %Stream.GlobalBinary:

Do strm.Rewind()
Set o = {}, o.strm = strm, strm2 = o.%Get("strm",,"stream>base64")
Set strm3 = ##class(%Stream.GlobalBinary).%New()
Do strm3.CopyFrom(strm2)

Since this issue can't be reproduced by you on another server, or by me with a fresh install of your adhoc, I think it's highly unlikely that there's a product defect. I think this is an issue with that specific instance only. The WRC should be able to help you investigate this further.

I tried to reproduce your issue with your exact server version and I couldn't get the error to occur. Do you remember when this started happening? Does debugging work when you connect to other instances?

Yes, that is very helpful. The <COMMAND> error is coming from a line that calls "Do <debug_target>", which in this case is "##class(prosthetic.ProstheticResourceTest).RunTests()". Does running "Set a = "##class(prosthetic.ProstheticResourceTest).RunTests()" Do @a" work from the terminal in that namespace or do you see the same <COMMAND>?