@whooshbang/contract-mock 1.0.0-rc.37 → 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.
- package/CHANGELOG.md +54 -0
- package/README.md +2 -0
- package/dist/core.js +1098 -122
- package/dist/core.js.map +1 -1
- package/dist/recipient-copy-defaults.d.ts +2002 -0
- package/dist/recipient-copy-defaults.js +2004 -0
- package/dist/recipient-copy-defaults.js.map +1 -0
- package/dist/types.d.ts +9 -4
- package/package.json +6 -5
- package/scenarios/v1/manifest.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,60 @@ recorded here.
|
|
|
5
5
|
|
|
6
6
|
## Unreleased
|
|
7
7
|
|
|
8
|
+
## 2.0.0-rc.5
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- Route a message the way the service does: a chosen `connection_id` is honored, and with none the subscriber's preferred channel, else the default connection when connected there, else the most recently connected one. A chosen connection that is unknown, archived or paused is `request_invalid` at `/connection_id`; one the subscriber never connected through is `subscriber_not_connected` (FXO-2865).
|
|
13
|
+
|
|
14
|
+
## 2.0.0-rc.4
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
|
|
18
|
+
- Match the shorter email reply guidance in all sixteen recipient languages (FXO-2806).
|
|
19
|
+
|
|
20
|
+
## 2.0.0-rc.3
|
|
21
|
+
|
|
22
|
+
### Added
|
|
23
|
+
|
|
24
|
+
- Match subscriber time-zone updates and effective-value precedence from the rc.3 contract (FXO-2806).
|
|
25
|
+
|
|
26
|
+
## 2.0.0-rc.2
|
|
27
|
+
|
|
28
|
+
### Changed
|
|
29
|
+
|
|
30
|
+
- Invite links default to 12 hours (43,200 seconds) and accept caller lifetimes
|
|
31
|
+
from 60 seconds to 7 days (604,800 seconds), by owner decision (FXO-2796).
|
|
32
|
+
|
|
33
|
+
### Added
|
|
34
|
+
|
|
35
|
+
- Match the 2.0.0-rc.2 text, image and recipient-copy contract (FXO-2778).
|
|
36
|
+
- Retain the complete subscriber-group and dashboard API parity release from rc.1.
|
|
37
|
+
|
|
38
|
+
## 2.0.0-rc.1
|
|
39
|
+
|
|
40
|
+
### Breaking
|
|
41
|
+
|
|
42
|
+
- Exercise `@whooshbang/contracts@2.0.0-rc.1` and `@whooshbang/sdk@2.0.0-rc.1`.
|
|
43
|
+
All subscriber-group public names match the service, without aliases
|
|
44
|
+
(FXO-2740). Slack link requests require `connection_id`.
|
|
45
|
+
|
|
46
|
+
### Added
|
|
47
|
+
|
|
48
|
+
- Filtered message listing, retained authored message/question/image reads,
|
|
49
|
+
delivery and interaction timelines, sender-name updates, customer-event
|
|
50
|
+
attempts/replay, delivery holds, machine-client inventory/revocation and the
|
|
51
|
+
complete sixteen-language recipient-copy catalogue (FXO-2743).
|
|
52
|
+
- Rich recorded connection tests with canonical content/question fingerprints.
|
|
53
|
+
Only the private recorded-test dispatch can target a spare connection;
|
|
54
|
+
ordinary sends continue to enforce notifier routing and recipient preference.
|
|
55
|
+
|
|
56
|
+
### Known limitation
|
|
57
|
+
|
|
58
|
+
- Subscriber channel-settings reads, binding transitions and preferred-binding
|
|
59
|
+
writes remain unsupported by the deterministic mock (FXO-2767). The published
|
|
60
|
+
API, SDK and MCP tools provide these operations against the real service.
|
|
61
|
+
|
|
8
62
|
## 1.0.0-rc.37
|
|
9
63
|
|
|
10
64
|
### Added
|
package/README.md
CHANGED
|
@@ -321,3 +321,5 @@ sending restrictions. With no authority fixture the operation refuses safely.
|
|
|
321
321
|
The mock keeps original consent and actor evidence on retries and rejects
|
|
322
322
|
conflicting consent, future timestamps and noncanonical addresses. These are
|
|
323
323
|
local fixtures; they never create provider resources or send email.
|
|
324
|
+
|
|
325
|
+
A `channelConnections` option seeds safe connection state when provider setup has already completed outside the mock. Each seed names its owning organization and carries a validated `ChannelConnection` in an existing project and environment. This supports customer email sender changes without inventing provider credentials or domain verification.
|