go to post Brett Saviano · Nov 3, 2021 Yes, that's expected behavior. The vscode-objectscript extension defines the languages based on file extensions: { "id": "objectscript", "aliases": [ "ObjectScript" ], "extensions": [ ".mac", ".int" ] }, { "id": "objectscript-class", "aliases": [ "ObjectScript Class" ], "extensions": [ ".cls" ] }, { "id": "objectscript-macros", "aliases": [ "ObjectScript Include" ], "extensions": [ ".inc" ] }, { "id": "objectscript-csp", "aliases": [ "ObjectScript CSP" ], "extensions": [ ".csp", ".csr" ] },
go to post Brett Saviano · Nov 3, 2021 Hi Julian, I just opened up my VS Code (version 1.61.2 on Mac, latest version of all 3 extensions) and tried formatting a class and mac routine and it worked both times. Can you confirm that the Language Server extension is enabled? Also, what's the extension of the file that you're trying to format?
go to post Brett Saviano · Nov 3, 2021 @Julian Matthews The Language Server extension includes an ObjectScript formatter with the following features: Normalize the case of ObjectScript commands, system functions and system variables. Normalize the usage of short or long versions of ObjectScript commands, system functions and system variables. You can invoke it like any other formatter in VS Code. This VS Code doc page has more information on formatting in VS Code. The Language Server README has more info on its features and configuration settings.
go to post Brett Saviano · Jun 17, 2021 @Muhammad Waseem Atelier is deprecated. VS Code is the recommended IDE for new ObjectScript developers. See this post for details.
go to post Brett Saviano · Jun 17, 2021 @Michael Lei SAM (or standalone Prometheus) can only monitor IRIS version 2020.1 or later.
go to post Brett Saviano · May 26, 2021 Do you have the file exported to your local file system already? If not, then you'll have to set the serverSideEditing setting to true for the server copy that gets opened to be editable.
go to post Brett Saviano · May 26, 2021 @Dominic Chui Please try issue #2 again using LS version 1.1.6 and vscode-objectscript version 1.0.11. To diagnose issue #1, I'll need the text of the routine that you're seeing the "class does not exist" error in. Please submit an issue at https://github.com/intersystems/language-server/issues with a code sample.
go to post Brett Saviano · May 26, 2021 @Peter Steiwer This is fixed in LS version 1.1.6 and vscode-objectscript version 1.0.11. When using those versions, the LS will check if you have a local copy of the file before opening the server copy. See https://github.com/intersystems/language-server/issues/45
