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
- New MarkLogic icon in the Activity Bar that can be used to open an explorer view with high-level information about the currently connected MarkLogic server.
4
+
- Can use new configuration options to connect to MarkLogic behind a proxy server or in MarkLogic Cloud.
5
+
* -restBasePath
6
+
* -manageBasePath
7
+
* -testBasePath
8
+
* -adminBasePath
9
+
* -apiKey
10
+
* -authType (now accepts "CLOUD")
11
+
-[Improved user guide.](https://marklogic.github.io/mlxprs/)
-[#116](https://github.com/marklogic/mlxprs/issues/116) Updated dependencies and fixed all known security vulnerabilities
28
-
-[#119](https://github.com/marklogic/mlxprs/issues/119) Added SJS binding to JavaScript language
29
-
-[#97](https://github.com/marklogic/mlxprs/issues/97) Added a configuration option for the MarkLogic Manage app server port (used for the SJS debug server port)
30
-
-[#117](https://github.com/marklogic/mlxprs/issues/117) Fixed a bug with the first attempt to eval a JavaScript tab
31
-
-[#109](https://github.com/marklogic/mlxprs/issues/109) Prevent the database param from being used in REST calls when the database setting is empty
40
+
-[#116](https://github.com/marklogic/mlxprs/issues/116) Updated dependencies and fixed all known security vulnerabilities.
41
+
-[#119](https://github.com/marklogic/mlxprs/issues/119) Added SJS binding to JavaScript language.
42
+
-[#97](https://github.com/marklogic/mlxprs/issues/97) Added a configuration option for the MarkLogic Manage app server port (used for the SJS debug server port).
43
+
-[#117](https://github.com/marklogic/mlxprs/issues/117) Fixed a bug with the first attempt to eval a JavaScript tab.
44
+
-[#109](https://github.com/marklogic/mlxprs/issues/109) Prevent the database param from being used in REST calls when the database setting is empty.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+86-8Lines changed: 86 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -52,11 +52,17 @@ cd server
52
52
npm install
53
53
cd ..
54
54
```
55
+
55
56
A shorthand script that does all of that for you is
56
57
```
57
58
npm run installAll
58
59
```
59
60
61
+
If you want to ensure a clean build, this command clears all transitory files
62
+
```
63
+
npm run cleanAll
64
+
```
65
+
60
66
## Using the Extension from the Project (except the debugger)
61
67
It is recommended to use VSCode as the editor for this package, as it can self-load a debug instance.
62
68
@@ -119,12 +125,40 @@ The project contains three test applications.
119
125
120
126
### Integration Testing Setup
121
127
122
-
JavaScript debugger integration testing requires a running MarkLogic server where you have full admin rights. Ideally, you should use a dedicated MarkLogic instance for this purpose. The tests assume the existence of a "mlxprs-test" application server running on port 8055 using the "mlxprs-test-content" and "mlxprs-test-modules" databases. Those values are set in test-app/gradle.properties and the admin password should be set in test-app/gradle-local.properties. Then you can use the following commands to build and configure the databases and application servers.
128
+
JavaScript debugger integration testing requires a running MarkLogic server where you have full admin rights. Ideally, you should use a dedicated MarkLogic instance for this purpose. The tests assume the existence of a "mlxprs-test" application server running on port 8055 using the "mlxprs-test-content" and "mlxprs-test-modules" databases. Those values are set in test-app/gradle.properties. Assuming you want the test application deployed locally, then in that gradle.properties file, ensure the "Local config" properties are uncommented and that the "Cloud config" properties are commented out.
129
+
```
130
+
# Local config
131
+
mlRestAuthentication=basic
132
+
mlHost=localhost
133
+
mlUsername=admin
134
+
mlPassword=changeme-in-gradle-local.properties
135
+
```
136
+
Additionally, the admin password should be set in test-app/gradle-local.properties. Then you can use the following commands to build and configure the databases and application servers.
123
137
```
124
138
cd test-app
125
139
./gradlew mlDeploy
126
140
```
127
141
142
+
Note that in order to facilitate testing the application with a proxy, the app-servers associated with the
143
+
test-app are set to use basic authentication. That includes a version of the Manage app-server on port 8059.
144
+
145
+
Once the app is deployed, ensure the workspace VSCode settings in test-app/.vscode/settings.json are set to
146
+
use the non-proxy settings as below, and not the reverse-proxy or cloud settings.
147
+
```
148
+
// Use these for non-proxy testing
149
+
"marklogic.host": "localhost",
150
+
"marklogic.ssl": false,
151
+
"marklogic.authType": "BASIC",
152
+
"marklogic.port": 8055,
153
+
"marklogic.restBasePath": "",
154
+
"marklogic.managePort": 8059,
155
+
"marklogic.manageBasePath": "",
156
+
"marklogic.testPort": 8054,
157
+
"marklogic.testBasePath": "",
158
+
"marklogic.adminPort": 8001,
159
+
"marklogic.adminBasePath": "",
160
+
```
161
+
128
162
### Manual Integration Testing
129
163
* Use the "Launch Extension (debug)" launch configuration in the "RUN AND DEBUG" window to open a new VS Code session.
130
164
* Once the new window is open, use "File -> Open Folder ..." menu to open the "test-app" folder as a separate project.
@@ -166,18 +200,55 @@ Note that the order of priority for setting the property values in the test code
166
200
167
201
168
202
### Testing from the command line
169
-
Run these two npm scripts from the command line in the root directory of the project to execute the tests. Note that VSCode must not be running while you run the tests.
203
+
Run these three npm scripts from the command line in the root directory of the project to execute the tests. Note that VSCode must not be running while you run the tests.
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ _Develop, run, and debug code for MarkLogic in the popular VS Code IDE_
16
16
* View modules (read-only) in the editor
17
17
* Run [marklogic-unit-test module](https://github.com/marklogic-community/marklogic-unit-test)
18
18
* Validate TDE templates and test the templates with node extraction
19
+
* View high-level information about the currently connected MarkLogic server
19
20
20
21
_JavaScript debugging requires version 2.0.0+ of the MarkLogic extension and [MarkLogic 10.0-4+](https://developer.marklogic.com/products/marklogic-server/10.0)._
0 commit comments