@rytass/bpm-core-client 0.1.6 → 0.1.8
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/CHANGELOG.md +27 -0
- package/README.md +7 -4
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
8
8
|
Releases are managed by [`nx release`](https://nx.dev/recipes/nx-release) with
|
|
9
9
|
Conventional Commits — see `nx.json` for the release config.
|
|
10
10
|
|
|
11
|
+
## 0.1.8 — 2026-05-28
|
|
12
|
+
|
|
13
|
+
### Documentation
|
|
14
|
+
|
|
15
|
+
- README "Organization Mirror Pattern" updated to match the
|
|
16
|
+
`@rytass/bpm-core-nestjs-module@0.1.8` README's clarification that
|
|
17
|
+
`metadataJson` is write-only — records returned by
|
|
18
|
+
`readOrganizationDashboard` don't surface metadata; reconcile by
|
|
19
|
+
`code` instead.
|
|
20
|
+
|
|
21
|
+
### Why a patch
|
|
22
|
+
|
|
23
|
+
No source change.
|
|
24
|
+
|
|
25
|
+
## 0.1.7 — 2026-05-28
|
|
26
|
+
|
|
27
|
+
### Documentation
|
|
28
|
+
|
|
29
|
+
- README "Current version" line refreshed to `0.1.7`.
|
|
30
|
+
- Org example continues to compile against the updated `OrgUnitType`
|
|
31
|
+
(UPPERCASE) — see `@rytass/bpm-core-shared@0.1.7` CHANGELOG for the
|
|
32
|
+
type-level change.
|
|
33
|
+
|
|
34
|
+
### Why a patch
|
|
35
|
+
|
|
36
|
+
No source change. Lockstep bump.
|
|
37
|
+
|
|
11
38
|
## 0.1.6 — 2026-05-28
|
|
12
39
|
|
|
13
40
|
### Added
|
package/README.md
CHANGED
|
@@ -18,7 +18,7 @@ functions directly from any framework (Next.js / Vite / Remix / plain Node).
|
|
|
18
18
|
|
|
19
19
|
## Package Status
|
|
20
20
|
|
|
21
|
-
Current version: `0.1.
|
|
21
|
+
Current version: `0.1.7`
|
|
22
22
|
|
|
23
23
|
The package intentionally stays framework-agnostic so it can be reused from
|
|
24
24
|
Next.js Server Components, Server Actions, plain React, or non-React
|
|
@@ -223,9 +223,12 @@ data in. Three rules keep the mirror idempotent:
|
|
|
223
223
|
1. **Use `code` as the natural key.** Both `OrgUnit` and `Position`
|
|
224
224
|
carry a unique `code` you control. On every sync, look up by `code`
|
|
225
225
|
before deciding INSERT vs UPDATE.
|
|
226
|
-
2.
|
|
227
|
-
|
|
228
|
-
|
|
226
|
+
2. **`metadataJson` is write-only.** The mutations accept it for audit
|
|
227
|
+
purposes — BPM stores the JSON verbatim — but the records returned
|
|
228
|
+
by `readOrganizationDashboard` do NOT include the metadata field
|
|
229
|
+
(kept out of paginated payloads). **Always reconcile by `code`**;
|
|
230
|
+
treat `metadataJson` as an audit/debugging breadcrumb, not a live
|
|
231
|
+
FK pointer.
|
|
229
232
|
3. **Soft-delete via the `delete*` mutations.** They set `deletedAt`;
|
|
230
233
|
live queries (`orgUnits`, `orgUnitCount`, etc.) filter soft-deleted
|
|
231
234
|
rows automatically.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@rytass/bpm-core-client",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"description": "Framework-agnostic TypeScript client for the Rytass BPM approval workflow GraphQL surface: fetch-based GraphQL transport, REST auth client, pre-baked typed operations for organization, member, form, template, and workflow.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"bpm",
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
}
|
|
74
74
|
},
|
|
75
75
|
"peerDependencies": {
|
|
76
|
-
"@rytass/bpm-core-shared": "^0.1.
|
|
76
|
+
"@rytass/bpm-core-shared": "^0.1.8"
|
|
77
77
|
},
|
|
78
78
|
"dependencies": {
|
|
79
79
|
"tslib": "^2.3.0"
|