|
12 | 12 |
|
13 | 13 | "workspaceFolder": "/home/irisowner/dev",
|
14 | 14 |
|
15 |
| - // This provides the elements of the connection object which require different values when connecting to the workspace within the container, |
16 |
| - // versus those in .vscode/settings.json which apply when operating locally on the workspace files. |
17 |
| - // We define and use a `server` so that (a) a user-level `objectscript.conn.server` properly doesn't override us, and (b) so InterSystems |
18 |
| - // Server Manager can also be used. |
19 |
| - "settings": { |
20 |
| - "objectscript.conn" :{ |
21 |
| - "server": "devcontainer", |
22 |
| - "active": true, |
23 |
| - }, |
24 |
| - "intersystems.servers": { |
25 |
| - "devcontainer": { |
26 |
| - "username": "SuperUser", |
27 |
| - "password": "SYS", |
28 |
| - "webServer": { |
29 |
| - "scheme": "http", |
30 |
| - "host": "127.0.0.1", |
31 |
| - "port": 52773 |
| 15 | + "customizations": { |
| 16 | + "vscode": { |
| 17 | + // This provides the elements of the connection object which require different values when connecting to the workspace within the container, |
| 18 | + // versus those in .vscode/settings.json which apply when operating locally on the workspace files. |
| 19 | + // We define and use a `server` so that (a) a user-level `objectscript.conn.server` properly doesn't override us, and (b) so InterSystems |
| 20 | + // Server Manager can also be used. |
| 21 | + "settings": { |
| 22 | + "objectscript.conn" :{ |
| 23 | + "server": "devcontainer", |
| 24 | + "active": true |
32 | 25 | },
|
| 26 | + "intersystems.servers": { |
| 27 | + "devcontainer": { |
| 28 | + "username": "SuperUser", |
| 29 | + "password": "SYS", |
| 30 | + "webServer": { |
| 31 | + "scheme": "http", |
| 32 | + "host": "127.0.0.1", |
| 33 | + "port": 52773 |
| 34 | + } |
| 35 | + } |
| 36 | + }, |
| 37 | + "python.defaultInterpreterPath":"/usr/irissys/bin/irispython" |
33 | 38 | },
|
34 |
| - }, |
35 |
| - "python.defaultInterpreterPath":"/usr/irissys/bin/irispython" |
36 |
| - }, |
37 |
| - |
38 |
| - // Add the IDs of extensions we want installed when the container is created. |
39 |
| - // Currently (March 2022) `intersystems.language-server` fails to run within the container (alpine platform). |
40 |
| - // Issue is probably https://github.com/intersystems/language-server/issues/185 and/or https://github.com/intersystems/language-server/issues/32 |
41 |
| - // Crash gets reported to the user, after which `intersystems-community.vscode-objectscript` falls back to |
42 |
| - // using its TextMate grammar for code coloring. |
43 |
| - "extensions": [ |
44 |
| - "ms-python.python", |
45 |
| - "ms-python.vscode-pylance", |
46 |
| - "intersystems-community.vscode-objectscript", |
47 |
| - "intersystems.language-server", |
48 |
| - "intersystems-community.servermanager", |
49 |
| - "ms-vscode.docker" |
50 |
| - ], |
| 39 | + // Add the IDs of extensions we want installed when the container is created. |
| 40 | + // Currently (March 2022) `intersystems.language-server` fails to run within the container (alpine platform). |
| 41 | + // Issue is probably https://github.com/intersystems/language-server/issues/185 and/or https://github.com/intersystems/language-server/issues/32 |
| 42 | + // Crash gets reported to the user, after which `intersystems-community.vscode-objectscript` falls back to |
| 43 | + // using its TextMate grammar for code coloring. |
| 44 | + "extensions": [ |
| 45 | + "ms-python.python", |
| 46 | + "ms-python.vscode-pylance", |
| 47 | + "intersystems-community.vscode-objectscript", |
| 48 | + "intersystems.language-server", |
| 49 | + "intersystems-community.servermanager", |
| 50 | + "ms-vscode.docker" |
| 51 | + ] |
| 52 | + } |
| 53 | + } |
51 | 54 | }
|
0 commit comments