@hogsend/cli 0.17.1 → 0.18.0
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hogsend/cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.18.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"tsup": "^8.5.1",
|
|
35
35
|
"tsx": "^4.22.4",
|
|
36
36
|
"vitest": "^4.1.7",
|
|
37
|
-
"@hogsend/studio": "^0.
|
|
37
|
+
"@hogsend/studio": "^0.18.0",
|
|
38
38
|
"@repo/typescript-config": "0.0.0"
|
|
39
39
|
},
|
|
40
40
|
"engines": {
|
|
@@ -44,8 +44,8 @@
|
|
|
44
44
|
"@clack/prompts": "^1.5.0",
|
|
45
45
|
"better-auth": "^1.6.11",
|
|
46
46
|
"picocolors": "^1.1.1",
|
|
47
|
-
"@hogsend/db": "^0.
|
|
48
|
-
"@hogsend/engine": "^0.
|
|
47
|
+
"@hogsend/db": "^0.18.0",
|
|
48
|
+
"@hogsend/engine": "^0.18.0"
|
|
49
49
|
},
|
|
50
50
|
"scripts": {
|
|
51
51
|
"prebuild": "node scripts/bundle-studio.mjs",
|
|
@@ -89,7 +89,7 @@ await hs.events.send({ // POST /v1/events
|
|
|
89
89
|
eventProperties: { source: "landing" }, // stored ON the event
|
|
90
90
|
contactProperties: { country: "GB" }, // merged onto the CONTACT
|
|
91
91
|
idempotencyKey: "evt_abc",
|
|
92
|
-
}); // -> { stored, exits, listsError? }
|
|
92
|
+
}); // -> { stored, exits, contactKey?, listsError? }
|
|
93
93
|
hs.events.track(/* … */); // alias of events.send
|
|
94
94
|
|
|
95
95
|
// Emails ------------------------------------------------------------------
|
|
@@ -185,13 +185,17 @@ same split is exposed by the CLI as `--prop` (event) vs `--contact-prop`
|
|
|
185
185
|
## The 202 + `listsError` warning
|
|
186
186
|
|
|
187
187
|
`POST /v1/events` returns **202 Accepted** (the event is durably stored and
|
|
188
|
-
queued for routing), NOT 200. The result is `{ stored, exits }`
|
|
189
|
-
`listsError`:
|
|
188
|
+
queued for routing), NOT 200. The result is `{ stored, exits, contactKey }`
|
|
189
|
+
plus an optional `listsError`:
|
|
190
190
|
|
|
191
191
|
- `stored` — `true` once the event row is written (`false` only on a dedup via
|
|
192
192
|
`idempotencyKey`).
|
|
193
193
|
- `exits` — the `{ journeyId, stateId, exited }[]` from evaluating active
|
|
194
194
|
journeys' `exitOn` rules for this user.
|
|
195
|
+
- `contactKey` — the contact's canonical key (engine ≥0.18): the same key
|
|
196
|
+
outbound destinations emit as `userId` and `hs_t` identity tokens resolve
|
|
197
|
+
to. Hand it to your analytics `identify()` to join the session to the
|
|
198
|
+
contact's person — it carries no PII.
|
|
195
199
|
- **`listsError?`** — present ONLY when the event was ingested fine but the
|
|
196
200
|
(non-atomic, post-ingest) `lists` membership write failed. **The event itself
|
|
197
201
|
is durably stored** — this is a soft warning surfaced on the 202, not a 400.
|