@rytass/bpm-core-shared 0.1.4 → 0.1.6
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 +33 -0
- package/package.json +1 -1
- package/src/lib/identity.d.ts +11 -0
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,39 @@ 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.6 — 2026-05-28
|
|
12
|
+
|
|
13
|
+
No source changes. Lockstep bump alongside
|
|
14
|
+
`@rytass/bpm-core-nestjs-module@0.1.6` (new `MemberNotFoundException`
|
|
15
|
+
export) and `@rytass/bpm-core-client@0.1.6` (new `configureBPMClient`).
|
|
16
|
+
|
|
17
|
+
## 0.1.5 — 2026-05-28
|
|
18
|
+
|
|
19
|
+
### Documentation
|
|
20
|
+
|
|
21
|
+
- **`MemberMetadata.customFields` JSDoc.** Documented as opaque
|
|
22
|
+
host-shaped JSON: BPM stores the object verbatim, serializes it back
|
|
23
|
+
to GraphQL clients via `MemberProfile.customFieldsJson`, and never
|
|
24
|
+
introspects keys. Hosts populate the field via the
|
|
25
|
+
`options.readCustomFields?.(member)` hook in
|
|
26
|
+
`createBPMMemberBaseResolverProvider`. This was previously implied by
|
|
27
|
+
the source but undocumented in the published JSDoc.
|
|
28
|
+
|
|
29
|
+
### Why a patch
|
|
30
|
+
|
|
31
|
+
No public type signatures change. JSDoc only.
|
|
32
|
+
|
|
33
|
+
## 0.1.4 — 2026-05-27
|
|
34
|
+
|
|
35
|
+
No source changes. Bumped in lockstep with
|
|
36
|
+
`@rytass/bpm-core-nestjs-module@0.1.4` (re-publish after the 0.1.3
|
|
37
|
+
backend tarball shipped only `.ts` source — see that package's CHANGELOG).
|
|
38
|
+
|
|
39
|
+
## 0.1.3 — 2026-05-27 (deprecated on npm)
|
|
40
|
+
|
|
41
|
+
Lockstep bump alongside the broken 0.1.3 backend release. Avoid;
|
|
42
|
+
upgrade directly to 0.1.4 or newer.
|
|
43
|
+
|
|
11
44
|
## 0.1.2 — 2026-05-27
|
|
12
45
|
|
|
13
46
|
No source changes. Bumped in lockstep with
|
package/package.json
CHANGED
package/src/lib/identity.d.ts
CHANGED
|
@@ -2,6 +2,17 @@ export interface MemberMetadata {
|
|
|
2
2
|
readonly memberId: string;
|
|
3
3
|
readonly name: string;
|
|
4
4
|
readonly email: string;
|
|
5
|
+
/**
|
|
6
|
+
* Opaque host-shaped JSON. BPM stores the object verbatim, serializes
|
|
7
|
+
* it back to GraphQL clients as `MemberProfile.customFieldsJson`, and
|
|
8
|
+
* never introspects keys — anything the host puts here flows through
|
|
9
|
+
* unchanged. Hosts using `createBPMMemberBaseResolverProvider` populate
|
|
10
|
+
* this field via the `options.readCustomFields?.(member)` hook;
|
|
11
|
+
* standalone `BPMMemberResolver` implementations return whatever shape
|
|
12
|
+
* the consumer UI needs. Use it as a side channel for picker labels,
|
|
13
|
+
* org context strings, avatar URLs, or any other host-specific
|
|
14
|
+
* metadata that should appear in member-display UIs.
|
|
15
|
+
*/
|
|
5
16
|
readonly customFields: Readonly<Record<string, unknown>>;
|
|
6
17
|
}
|
|
7
18
|
export interface MemberMetadataCacheEntry {
|