@whooshbang/sdk 2.0.0-rc.4 → 2.0.0-rc.5

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.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -412,8 +412,8 @@ code throws from that same method.
412
412
  | `project_slug_conflict` | Exception | The slug is already taken in this organization. Refused input, handled as `request_invalid` is: choose another. |
413
413
  | `request_invalid` | Exception | The request broke a documented bound. `fieldErrors` names each field. |
414
414
  | `replay_unavailable` | Exception | A customer-event replay was refused by the attempt's state. The caller waits for a terminal attempt or accepts that an aged-out payload is gone; there is nothing to branch on. |
415
- | `subscriber_unbound` | Outcome | On a send, the person's channel state: they revoked their channel or never finished subscribing, so the branch is to invite them again. The service uses the same code when a `connection_id` does not route to the subscriber or the connection behind them was archived, which an invitation does not fix; `problem.diagnostic_id` tells support which. `createMessage` and `createMessageInEnvironment` return it. `createMachineClient` still throws it: a machine client for an unbound subscriber is setup that is wrong. |
416
- | `subscriber_not_connected` | Exception | A connection test named a subscriber who has not connected through that connection. `problem.subscriber_id` and `problem.channel` say who and where; nothing was sent. The caller picks another subscriber or invites this one through the connection. |
415
+ | `subscriber_unbound` | Outcome | On a send, the person's channel state: they revoked their channel or never finished subscribing, so the branch is to invite them again. It is also the answer when a send names a `connection_id` and the subscriber has no connected channel at all. `createMessage` and `createMessageInEnvironment` return it. `createMachineClient` still throws it: a machine client for an unbound subscriber is setup that is wrong. |
416
+ | `subscriber_not_connected` | Exception | A send or a connection test named a connection the subscriber has not connected through, while they are connected through another. `problem.subscriber_id` and `problem.channel` say who and where; nothing was sent. Naming the connection was the caller's choice: omit `connection_id` to let the service choose one of their channels, pick a connection they connected through, or invite them through this one. |
417
417
  | `recipient_configuration_invalid` | Exception | The owner's recipient-experience configuration is not usable as submitted or as stored. |
418
418
  | `recipient_origin_forbidden` | Exception | The presenting browser origin is not registered for the session. |
419
419
  | `return_destination_not_found` | Exception | The return-destination key is not configured. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@whooshbang/sdk",
3
- "version": "2.0.0-rc.4",
3
+ "version": "2.0.0-rc.5",
4
4
  "description": "JavaScript client and browser recipient settings UI for WhooshBang V1",
5
5
  "private": false,
6
6
  "license": "MIT",
@@ -64,7 +64,7 @@
64
64
  "type-check": "tsc --noEmit -p tsconfig.json"
65
65
  },
66
66
  "dependencies": {
67
- "@whooshbang/contracts": "2.0.0-rc.4"
67
+ "@whooshbang/contracts": "2.0.0-rc.5"
68
68
  },
69
69
  "engines": {
70
70
  "node": ">=22.13.0"