You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-13Lines changed: 28 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,9 @@ Once you clone the new repo to your laptop and open VSCode (with the [InterSyste
22
22
Make sure you have [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) and [Docker desktop](https://www.docker.com/products/docker-desktop) installed.
THe sample repository contains two simplest examples of ObjectScript classes: ObjectScript method that returns value and method that creates a persistent record.
48
-
1.
49
-
Open IRIS terminal and run the ObjectScript Test() method to see if runs the script and returns values from IRIS:
53
+
54
+
1.Open IRIS terminal and run the ObjectScript Test() method to see if runs the script and returns values from IRIS:
This repository is ready to code in VSCode with ObjectScript plugin.
86
+
87
+
This repository is ready to code in VSCode with the ObjectScript plugin.
88
+
79
89
Install [VSCode](https://code.visualstudio.com/), [Docker](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) and the [InterSystems ObjectScript Extension Pack](https://marketplace.visualstudio.com/items?itemName=intersystems-community.objectscript-pack) plugin and open the folder in VSCode.
80
-
Open /src/cls/PackageSample/ObjectScript.cls class and try to make changes - it will be compiled in running IRIS docker container.
90
+
91
+
Open the `/src/cls/PackageSample/ObjectScript.cls` class and make changes - it will be compiled in the running IRIS docker container.
Feel free to delete PackageSample folder and place your ObjectScript classes in the form
84
-
/src/organisation/package/Classname.cls
85
-
[Read more about folder setup for InterSystems ObjectScript](https://community.intersystems.com/post/simplified-objectscript-source-folder-structure-package-manager)
86
-
and her on the [naming convention]()
95
+
Feel free to delete the PackageSample folder and place your ObjectScript classes in the form
96
+
`/src/organisation/package/Classname.cls`
97
+
98
+
[Read more about folder setup for InterSystems ObjectScript](https://community.intersystems.com/post/simplified-objectscript-source-folder-structure-package-manager)and here on the [naming convention]()
87
99
88
100
## Running unit tests
89
-
The template contains to test classes: `TestObjectScript.cls` and `TestPersistentClass.cls `
90
-
To run the unit tests we can use Package Manager environment.
101
+
102
+
The template contains two test classes: `TestObjectScript.cls` and `TestPersistentClass.cls `
103
+
104
+
To run the unit tests we can use the Package Manager environment.
91
105
92
106
```
93
107
IRISAPP>zpm
@@ -136,7 +150,8 @@ All PASSED
136
150
zpm:IRISAPP>
137
151
```
138
152
139
-
In case of test errors you can check it back in the UnitTest portal, that can be easily opened via ObjectScript menu in VSCode:
153
+
In case of test errors, you can find more details back in the UnitTest portal, which can be easily opened via ObjectScript menu in VSCode:
0 commit comments