go to post Brett Saviano · Mar 9, 2023 @Norman W. Freeman This query will return the names of all non-system and non-generated classes in the current namespace: SELECT Name FROM %Library.RoutineMgr_StudioOpenDialog('*.cls',1,1,0,1,0,0) The documentation for this query and its parameters can be found here.
go to post Brett Saviano · Mar 6, 2023 The vscode-objectscript extension now contains a snippet for custom class queries. It was added by pull request #1111 and if you want to try this snippet before the next release you can download the beta version of the extension found here.
go to post Brett Saviano · Mar 6, 2023 @Robert Cemper We currently don't have equivalents for Studio Wizards. There is a snippet for a %SQLQuery but not for %Query. Please file an enhancement request issue and we can consider adding a snippet or maybe a very simple UI.
go to post Brett Saviano · Feb 28, 2023 @Ben Spead The existing docs here have been updated to reflect the new UI.
go to post Brett Saviano · Feb 28, 2023 I expect that this will work fine. Our 'Open Error Location..." command just goes to the line+offset in the INT routine, it doesn't try to resolve the location in the CLS/MAC/CSP that generated the INT.
go to post Brett Saviano · Feb 14, 2023 Here's a full list of all the MimeTypes that will be correctly colored in VS Code (requires InterSystems Langauge Server version 2.1.1): application/json text/html text/javascript text/css application/sql text/x-java-source application/python text/x-python text/xml application/xml An XData bock with no MimeType will still be colored as XML.
go to post Brett Saviano · Feb 6, 2023 @Scott Roth Please see our documentation page on server-side editing for directions for setting up your workspace.
go to post Brett Saviano · Jan 4, 2023 @Rob Schoenmakers @Joel Solon I just released InterSystems Language Server version 2.2.0, which provides intellisense for variables created by %New(), %Open() or %OpenId(). VS Code should auto-update it for you.
go to post Brett Saviano · Oct 5, 2022 Maybe try using 'ck' instead of 'cuk'. The 'u' flag is the one that tells the compiler to not recompile if it doesn't detect a code change.
go to post Brett Saviano · Oct 5, 2022 @Zach McKinney Thanks for log output. Have you compiled that class? The "Breakpoint Cannot Be Mapped" error means that the debugger couldn't map that location in that class to the generated INT routine.
go to post Brett Saviano · Oct 1, 2022 @Zach McKinney Please follow the steps listed here and send me the log output. Feel free to mask any sensitive information.
go to post Brett Saviano · Sep 23, 2022 I opened a pull request to improve the documentation so other users don't have the same confusion
go to post Brett Saviano · Sep 23, 2022 That's the problem. The folder setting is relative to your workspace root. Since you have repos open, you want it to be "PATS\Server\Namespaces\AXIS".
go to post Brett Saviano · Sep 23, 2022 Did you export those files using the VS Code extension? The extension uses its export settings to determine where it will look for local copies. For example, if you have the AXIS folder open in VS Code you would need the following export settings to reflect the existing folder structure that you have: objectscript.export.folder setting equal to "", objectscript.export.atelier setting set to true, and objectscript.export.addCategory setting set to false.
go to post Brett Saviano · Sep 23, 2022 @Michael Hampton I need more info about your exact setup to answer your question. What were your export settings previously? What folder within your workspace are your InterSystems files in? Are you sure that the file that contains the definition has a local copy?
go to post Brett Saviano · Aug 23, 2022 @Scott Roth The custom metrics code needs to be added to the instances of IRIS that SAM is monitoring, not the SAM Manager IRIS instance itself. The full documentation for adding custom metrics can be found here.
go to post Brett Saviano · Aug 19, 2022 I believe this is the same problem described here. You need to add the --check-caps false command to the iris container in your docker-compose.yml file, like this: ... iris: command: --check-caps false init: true ... The SAM 1.1 distribution should have this done for you but that change must not have made it in. I think you can still enter the SAM 2.0 EAP if you'd like to start with the upcoming version.
go to post Brett Saviano · Aug 19, 2022 The logs are stored in the containers themselves. Using docker you can read them using the docker logs command. According to the podman docs, this is what you would need to run: podman logs sam_iris_1
go to post Brett Saviano · Aug 19, 2022 @Scott Roth I don't use podman so I'm not sure how to check this but it looks like the SAM Manager container (a modified IRIS) is not up or is not healthy. Can you check if it's up and if so, check the log contents? Nginx is probably reporting a bad gateway error because the SAM Manager isn't listening on the expected port
