VSCode New Files

Question

Question

The company I work for have a repository for one of our products which already contains both InterSystems and non-InterSystems source code. I'm in the process of trying to migrate us over to using VSCode to edit the InterSystems source but am stuck on some issues surrounding the files on disk and the routines in the IRIS instance.

The folder structure inside the repo is \appname\src\database. Directly underneath the database folder is all of our InterSystems source code. If I add a new routine to the root of the database folder called ROUTINEA.int, the created routine ends up being prefixed with "src.database."

In VS Code it looks like this:

In IRIS Studio it looks like this:

I don't want new routines to live in a package within IRIS called src.database.

My workspace file looks like this:

{
"folders": [
    {
      "path": "."
    }
],
"settings": {
    "objectscript.conn": {
      "server": "iris",
      "ns": "{namespace}",
      "active": true
    },
    "objectscript.export": {
      "folder": "src/database",
      "addCategory": false,
      "map": {},
      "atelier": true,
      "generated": false,
      "filter": "",
      "exactFilter": "",
      "category": "*",
      "noStorage": false,
      "dontExportIfNoChanges": false,
      "maxConcurrentConnections": 0,
      "mapped": true
    }
}
}

I've tried all the things I can think of to alter the workspace settings but am totally stuck on how to make VSCode know that the database folder is the root folder. I've even had a look through the github repos to see if I can track down what is going on. I should also add that I don't want to move the workspace file to within the database folder, whilst it would resolve this issue, it introduces another issue in that the developer can't select the database folder to import and compile all contents. Has anyone else tackled this issue?

Any help would be much appreciated.

Product version: IRIS 2022.1

$ZV: IRIS for Windows (x86-64) 2022.1.4 (Build 812_0_22849) Wed Nov 8 2023 17:54:43 EST

Discussion (9)4

Log in or sign up to continue

John Murray · Jan 18

I'm guessing that Brett is testing on a non-Windows platform. By replicating Mathew's setup on Windows I can reproduce the issue.

Mathew, please try using backslash in the "folder" property of your "objectscript.export" settings object:

      "folder": "src\\database",

2 0

score 0 · Answer 1 · 2024-01-17T11:26:33-05:00

@Mathew Rimmington
Based on your description, I think that your setting for "objectscript.export.folder" should be "appname/src/database" instead of "src/database".

score 0 · Answer 2 · 2024-01-17T12:21:29-05:00

Hi @Brett Saviano, just tried it but made no difference sadly. New routines are still created in package src.database.

score 0 · Answer 3 · 2024-01-17T15:32:49-05:00

I just created a code-workspace file using your example above and I couldn't reproduce this is it possible that there's a .vscode/settings.json inside the "." folder that contains different objectscript.export settings? If so, those will take precedence. Folder-specific settings take precedence over workspace-specific settings, and workspace-specific take precdence over user-specific.

score 0 · Answer 4 · 2024-01-18T04:23:32-05:00

In the repository root there is a .vscode/settings.json file but it doesn't override any export settings. It looks like this:

{

"objectscript.conn": {

"server": "iris",

"ns": "{namespace}",

"active": true

}

score 0 · Answer 5 · 2024-01-18T04:28:11-05:00

As an experiment, I did try switching the folder structure to appname/database/src. I also changed the objectscript.export.folder setting to match the new structure. This does resolve the issue.

Is there some hardcoding of the "src" folder perhaps in the extension?

The trouble is, I can't leave the folder structure like this.

score 1 · Answer 6 · 2024-01-18T07:19:43-05:00

Mathew Rimmington · Jan 18

Hi @John Murray, thanks so much for this. I can confirm that this fixes the issue.

1 0

score 0 · Answer 7 · 2024-01-18T07:51:23-05:00

It's interesting to note it must be double backslash. I had mine as "src/database" as well and that does not work for new files but works for the "goto to definition" feature. I'm guessing some of these are normalised and some are not.

score 0 · Answer 8 · 2024-01-18T07:15:37-05:00

Mathew Rimmington · Jan 18

Removed - posted at the same time as John Murray's answer above.

0 0