Stefan, it sounds like you could benefit from using the server-side editing capabilities of this extension, in combination with server-side source control such as Deltanji from George James Software (for whom I work). Properly implemented, server-side source control will also control people who edit using Portal and Studio, or who use our Serenji extension for VS Code instead of the InterSystems one.
That setting affects how the ObjectScript Explorer behaves. That's the tree you get if there's an InterSystems logo on your Activity Bar and you click on it. It's the tree whose primary purpose is to let you export server code into files on your workstation that you then edit locally, probably add to a Git repo, and import to your server to run and debug it.
When you select a class or routine in that tree, and it only exists on the server (i.e. it isn't one that you have already exported locally), then the above setting dictates whether the code is opened read-only or editable.
IMO storing a password in plaintext like this should only be used as a last resort, or when the password is the default one for a built-in username. In all other cases I recommend using Server Manager's ability to store the password in your workstation's keychain.
Not yet fully documented is the facility to extend the 'Server Actions' quickpick which appears when you click the ObjectScript connection panel on the status bar.
go to post
Stefan, it sounds like you could benefit from using the server-side editing capabilities of this extension, in combination with server-side source control such as Deltanji from George James Software (for whom I work). Properly implemented, server-side source control will also control people who edit using Portal and Studio, or who use our Serenji extension for VS Code instead of the InterSystems one.
go to post
Try adding a space between iris and session
go to post
Surely an annual salary.
go to post
That's the MultiValue command. This is the doc for the ObjectScript one:
https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=RC...
go to post
go to post
That setting affects how the ObjectScript Explorer behaves. That's the tree you get if there's an InterSystems logo on your Activity Bar and you click on it. It's the tree whose primary purpose is to let you export server code into files on your workstation that you then edit locally, probably add to a Git repo, and import to your server to run and debug it.
When you select a class or routine in that tree, and it only exists on the server (i.e. it isn't one that you have already exported locally), then the above setting dictates whether the code is opened read-only or editable.
go to post
As @Dmitry Maslennikov said, you opened it in the Developer Community repo, here:
https://github.com/intersystems-community/developer-community/issues/654
But you need to open it in the extension's repo, here:
https://github.com/intersystems-community/vscode-objectscript
go to post
Does your new routine also appear in the ^rINDEX global?
go to post
IMO storing a password in plaintext like this should only be used as a last resort, or when the password is the default one for a built-in username. In all other cases I recommend using Server Manager's ability to store the password in your workstation's keychain.
go to post
Not yet fully documented is the facility to extend the 'Server Actions' quickpick which appears when you click the ObjectScript connection panel on the status bar.
Some pointers exist at https://github.com/intersystems-community/vscode-objectscript/issues/667...