oro-sdk 2.2.1 → 2.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +26 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -11,6 +11,7 @@ ORO SDK package is intended to be run in browser only. It contains everything ne
|
|
|
11
11
|
## Local development
|
|
12
12
|
|
|
13
13
|
> If you cannot see Jest types try opening this folder in a seperate VSCode window.
|
|
14
|
+
|
|
14
15
|
### Set up project
|
|
15
16
|
|
|
16
17
|
```bash
|
|
@@ -29,6 +30,7 @@ npm build # build
|
|
|
29
30
|
#### First you need to publish locally the `oro-sdk`
|
|
30
31
|
|
|
31
32
|
Two cases are possible:
|
|
33
|
+
|
|
32
34
|
1. You are updating `oro-apis/sdk/ts`:
|
|
33
35
|
|
|
34
36
|
In **`oro-apis/sdk/ts`**:
|
|
@@ -37,6 +39,7 @@ Two cases are possible:
|
|
|
37
39
|
npm install
|
|
38
40
|
npm run link:watch
|
|
39
41
|
```
|
|
42
|
+
|
|
40
43
|
2. You are updating `oro-apis/sdk/apis`:
|
|
41
44
|
|
|
42
45
|
In **`oro-apis/sdk/apis`**:
|
|
@@ -62,3 +65,26 @@ In **`oro-apps/web`**:
|
|
|
62
65
|
npm uninstall oro-sdk # optional
|
|
63
66
|
npm run dev:link
|
|
64
67
|
```
|
|
68
|
+
|
|
69
|
+
### Publishing package
|
|
70
|
+
|
|
71
|
+
1. (Only first time) Locally run `npm login` and use the creds in 1password (tech-team-oro) . This will create ~/.npmrc . You will require a OTP but it's sent on tech@orohealth.me so you should all have it.
|
|
72
|
+
2. Run `docker-compose up --build sdk-publisher`
|
|
73
|
+
|
|
74
|
+
#### Versioning of `oro-sdk` and `oro-sdk-apis`
|
|
75
|
+
|
|
76
|
+
As `oro-sdk-apis` is a dependency of `oro-sdk`, if you do some changes on `oro-sdk-apis` you will need to update `oro-sdk` and web app as well.
|
|
77
|
+
|
|
78
|
+
The versionning should be the same for `oro-sdk-apis` and `oro-sdk`. In other words, as we are using semantic versioning if we update patch/minor/major version of `oro-sdk-apis` we must update the same on `oro-sdk`.
|
|
79
|
+
|
|
80
|
+
>Example:
|
|
81
|
+
>
|
|
82
|
+
>I want to update the minor version of `oro-sdk-apis`: 1.2.5 -> 1.3.0
|
|
83
|
+
>
|
|
84
|
+
>Then I also need to update `package.json` of `oro-sdk` with the dependency `oro-sdk-apis@1.3.0` and I update the minor version of `oro-sdk`: 2.3.2 -> 2.4.0
|
|
85
|
+
|
|
86
|
+
You then need to publish packages in following order: `oro-sdk-apis`, `oro-sdk`:
|
|
87
|
+
|
|
88
|
+
Then, you update web app dependencies with `oro-sdk@2.4.0`
|
|
89
|
+
|
|
90
|
+
Done.
|
package/package.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "2.
|
|
2
|
+
"version": "2.5.1",
|
|
3
3
|
"main": "dist/index.js",
|
|
4
4
|
"typings": "dist/index.d.ts",
|
|
5
5
|
"files": [
|
|
@@ -59,7 +59,7 @@
|
|
|
59
59
|
"form-data": "^4.0.0",
|
|
60
60
|
"formdata-node": "^4.3.1",
|
|
61
61
|
"idb-keyval": "^5.0.6",
|
|
62
|
-
"oro-sdk-apis": "1.
|
|
62
|
+
"oro-sdk-apis": "1.3.0",
|
|
63
63
|
"oro-toolbox": "0.0.6",
|
|
64
64
|
"uuid": "^8.3.2"
|
|
65
65
|
}
|