Skip to content

Commit 8642985

Browse files
authored
Documentation & apidoc refactor 5.0 (#1062)
* Apidoc and documentation fixes for 5.0 * Review comments
1 parent 663bb4f commit 8642985

File tree

19 files changed

+130
-130
lines changed

19 files changed

+130
-130
lines changed

CONTRIBUTING.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,12 +51,16 @@ All PRs follow the same process:
5151
That includes descriptive commit messages.
5252
5. Please keep your PRs as small as possible, _i.e._ if you plan to perform a huge change,
5353
do not submit a single and large PR for it. For an enhancement or larger feature, you can create a GitHub issue first to discuss.
54-
6. Before you push, run these commands in your terminal to check if there are any errors:
54+
6. Before you push, you can run these commands in your terminal to check if there are any errors:
5555
* `npm install`: Installs dependencies
5656
* `npm run compile`: Compiles TypeScript into JavaScript, checking for any errors along the way
57-
* `npm run lint`: Runs linting to find stylistic/structural errors in the code
57+
* `npm run lint`: Runs linting to find stylistic/structural errors in the code and markdown files
5858
* `npm run validate-user-code`: Checks the validity of generated TypeScript type declaration files
59-
* `npm run test`: Runs unit and integration tests against the generated JavaScript code(the generated code is in `lib/` folder)
59+
* `npm run check-markdown-links <FILE>`: Checks for broken links in a markdown.
60+
Example usage: `npm run check-markdown-links DOCUMENTATION.md`
61+
* `npm run test:unit`: Runs unit tests against the generated JavaScript code (the generated code is in `lib/` folder)
62+
* `npm run test:integration`(SLOW): Runs integration tests against the generated JavaScript code
63+
(the generated code is in `lib/` folder)
6064
Push your PR once it is free of errors.
6165
7. If you submit a PR as the solution to a specific issue, please mention the issue number either in the PR description
6266
or commit message.

DOCUMENTATION.md

Lines changed: 77 additions & 82 deletions
Large diffs are not rendered by default.

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -23,20 +23,20 @@
2323
[Hazelcast](https://hazelcast.com/) is an open-source distributed in-memory data store and computation platform that
2424
provides a wide variety of distributed data structures and concurrency primitives.
2525

26-
Hazelcast Node.js client is a way to communicate to Hazelcast IMDG clusters and access the cluster data.
26+
Hazelcast Node.js client is a way to communicate to Hazelcast clusters and access the cluster data.
2727
The client provides a Promise-based API with a builtin support for native JavaScript objects.
2828

2929
## Installation
3030

3131
### Hazelcast
3232

33-
Hazelcast Node.js client requires a working Hazelcast IMDG cluster to run. This cluster handles the storage and
33+
Hazelcast Node.js client requires a working Hazelcast cluster to run. This cluster handles the storage and
3434
manipulation of the user data.
3535

36-
A Hazelcast IMDG cluster consists of one or more cluster members. These members generally run on multiple virtual or
36+
A Hazelcast cluster consists of one or more cluster members. These members generally run on multiple virtual or
3737
physical machines and are connected to each other via the network. Any data put on the cluster is partitioned to
3838
multiple members transparent to the user. It is therefore very easy to scale the system by adding new members as
39-
the data grows. Hazelcast IMDG cluster also offers resilience. Should any hardware or software problem causes a crash
39+
the data grows. Hazelcast cluster also offers resilience. Should any hardware or software problem causes a crash
4040
to any member, the data on that member is recovered from backups and the cluster continues to operate without any
4141
downtime.
4242

@@ -48,7 +48,7 @@ docker run -p 5701:5701 hazelcast/hazelcast:4.1.1
4848
```
4949

5050
You can also use our ZIP or TAR [distributions](https://hazelcast.com/open-source-projects/downloads/)
51-
as described [here](DOCUMENTATION.md#121-setting-up-a-hazelcast-imdg-cluster).
51+
as described [here](DOCUMENTATION.md#121-setting-up-a-hazelcast-cluster).
5252

5353
### Client
5454

@@ -84,7 +84,7 @@ await client.shutdown();
8484
> Refer to the [Code Samples section](https://github.com/hazelcast/hazelcast-nodejs-client/tree/master/code_samples)
8585
> to see samples with the complete code.**
8686
87-
If you are using Hazelcast IMDG and the Node.js client on the same machine, the default configuration should work
87+
If you are using Hazelcast and the Node.js client on the same machine, the default configuration should work
8888
out-of-the-box. However, you may need to configure the client to connect to cluster nodes that are running on
8989
different machines or to customize client properties.
9090

@@ -147,7 +147,7 @@ We encourage any type of contribution in the form of issue reports or pull reque
147147

148148
For issue reports, please share the following information with us to quickly resolve the problems.
149149

150-
* Hazelcast IMDG and the client version that you use
150+
* Hazelcast and the client version that you use
151151
* General information about the environment and the architecture you use like Node.js version, cluster size,
152152
number of clients, Java version, JVM parameters, operating system etc.
153153
* Logs and stack traces, if any.
@@ -180,7 +180,7 @@ Following command starts the tests:
180180
npm test
181181
```
182182

183-
Test script automatically downloads `hazelcast-remote-controller` and Hazelcast IMDG. The script uses Maven to download those.
183+
Test script automatically downloads `hazelcast-remote-controller` and Hazelcast. The script uses Maven to download those.
184184

185185
In order to run specific tests, you can give a pattern to the test command like the following:
186186

benchmark/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Simple benchmark for Hazelcast IMDG Node.js Client
1+
# Simple benchmark for Hazelcast Node.js Client
22

33
A simple benchmark that runs operations on `Map` concurrently, measures the execution time and calculates the throughput:
44
* `set` - runs `map.set(key, value)` operations.
@@ -17,7 +17,7 @@ Then, build the client (compile TypeScript):
1717
npm run compile
1818
```
1919

20-
Next, run at least one instance of IMDG. The most simple way to do it would be to use the
20+
Next, run at least one instance of Hazelcast. The most simple way to do it would be to use the
2121
[official Docker image](https://hub.docker.com/r/hazelcast/hazelcast/):
2222
```bash
2323
docker run --net=host hazelcast/hazelcast:4.1.1

code_samples/jaas_sample/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
This code sample demonstrates how to assign different permission policies for different user groups with the
44
Hazelcast's JAAS based security features.
5-
Security features used in this code sample requires **Hazelcast IMDG Enterprise** edition.
5+
Security features used in this code sample requires **Hazelcast Enterprise** edition.
66

77
---
88

code_samples/jaas_sample/hazelcast-member/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
Make sure you have
22
* [Java 8+](https://www.java.com/en/download/) installed on your system.
3-
* [Hazelcast IMDG Enterprise JAR](https://hazelcast.com/download/) available in your system.
3+
* [Hazelcast Enterprise JAR](https://hazelcast.com/download/) available in your system.
44

5-
Then, put your Hazelcast IMDG Enterprise license key into the [hazelcast.xml](src/main/resources/hazelcast.xml).
5+
Then, put your Hazelcast Enterprise license key into the [hazelcast.xml](src/main/resources/hazelcast.xml).
66

77
Compile the Java files with the following command:
88

package.json

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@
2222
"eslint-plugin-mocha": "~8.1.0",
2323
"husky": "^6.0.0",
2424
"jsonschema": "~1.4.0",
25+
"markdown-link-check": "^3.8.7",
2526
"markdownlint-cli": "^0.28.1",
2627
"mocha": "~8.4.0",
2728
"mocha-jenkins-reporter": "^0.4.6",
@@ -59,6 +60,7 @@
5960
"lint-markdown:fix": "markdownlint -f --ignore node_modules '**/*.md'",
6061
"startrc": "node scripts/test-runner.js startrc",
6162
"check-code-samples": "node scripts/test-runner.js check-code-samples",
63+
"check-markdown-links": "markdown-link-check -q",
6264
"prepare": "husky install"
6365
},
6466
"repository": {

src/core/RestValue.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ export const REST_VALUE_FACTORY_ID = -25;
2323
export const REST_VALUE_CLASS_ID = 1;
2424

2525
/**
26-
* Wrapper for values stored via IMDG REST API.
26+
* Wrapper for values stored via Hazelcast REST API.
2727
*/
2828
export class RestValue implements IdentifiedDataSerializable {
2929

src/core/SimpleEntryView.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ export class SimpleEntryView<K, V> {
5757
lastAccessTime: Long;
5858

5959
/**
60-
* Last time the value was flushed to mapstore.
60+
* Last time the value was flushed to map store.
6161
*/
6262
lastStoredTime: Long;
6363

src/proxy/FencedLock.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ import {DistributedObject} from '../core';
2525
* failures and network partitions. If a network partition occurs, it remains
2626
* available on at most one side of the partition.
2727
*
28-
* FencedLock works on top of CP sessions. Please refer to CP Session
29-
* IMDG documentation section for more information.
28+
* FencedLock works on top of CP sessions. Please refer to Hazelcast CP Session
29+
* documentation section for more information.
3030
*
3131
* Important note: FencedLock is non-reentrant. Once a caller acquires
3232
* the lock, it can not acquire the lock reentrantly. So, the next acquire

0 commit comments

Comments
 (0)