@hydranium/protocol 1.0.0-next.7 → 1.0.0-next.71

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 (104) hide show
  1. package/README.md +35 -1
  2. package/lib/client/data-connection.d.ts +103 -0
  3. package/lib/client/data-connection.d.ts.map +1 -0
  4. package/lib/client/data-connection.js +114 -0
  5. package/lib/client/data-connection.js.map +1 -0
  6. package/lib/client/data-events.d.ts +9 -1
  7. package/lib/client/data-events.d.ts.map +1 -1
  8. package/lib/client/data-events.js +14 -0
  9. package/lib/client/data-events.js.map +1 -1
  10. package/lib/client/data-port.d.ts +16 -21
  11. package/lib/client/data-port.d.ts.map +1 -1
  12. package/lib/client/data-session.d.ts +83 -78
  13. package/lib/client/data-session.d.ts.map +1 -1
  14. package/lib/client/data-session.js +81 -108
  15. package/lib/client/data-session.js.map +1 -1
  16. package/lib/client/index.d.ts +10 -7
  17. package/lib/client/index.d.ts.map +1 -1
  18. package/lib/client/index.js +10 -7
  19. package/lib/client/index.js.map +1 -1
  20. package/lib/client/message-relay.d.ts +8 -2
  21. package/lib/client/message-relay.d.ts.map +1 -1
  22. package/lib/client/message-relay.js +10 -4
  23. package/lib/client/message-relay.js.map +1 -1
  24. package/lib/client/rpc-connection.d.ts +139 -0
  25. package/lib/client/rpc-connection.d.ts.map +1 -0
  26. package/lib/client/rpc-connection.js +171 -0
  27. package/lib/client/rpc-connection.js.map +1 -0
  28. package/lib/client-ids.d.ts +41 -0
  29. package/lib/client-ids.d.ts.map +1 -0
  30. package/lib/client-ids.js +44 -0
  31. package/lib/client-ids.js.map +1 -0
  32. package/lib/data/data-protocol-methods.d.ts +2 -2
  33. package/lib/data/data-protocol-methods.d.ts.map +1 -1
  34. package/lib/data/data-protocol-methods.js +6 -1
  35. package/lib/data/data-protocol-methods.js.map +1 -1
  36. package/lib/data/data-server-protocol.d.ts +34 -1
  37. package/lib/data/data-server-protocol.d.ts.map +1 -1
  38. package/lib/data/events.d.ts +70 -3
  39. package/lib/data/events.d.ts.map +1 -1
  40. package/lib/errors.d.ts +25 -6
  41. package/lib/errors.d.ts.map +1 -1
  42. package/lib/errors.js +32 -12
  43. package/lib/errors.js.map +1 -1
  44. package/lib/index.d.ts +2 -0
  45. package/lib/index.d.ts.map +1 -1
  46. package/lib/index.js +5 -0
  47. package/lib/index.js.map +1 -1
  48. package/lib/messages/index.d.ts +28 -0
  49. package/lib/messages/index.d.ts.map +1 -0
  50. package/lib/messages/index.js +52 -0
  51. package/lib/messages/index.js.map +1 -0
  52. package/lib/messages/primitives.d.ts +141 -0
  53. package/lib/messages/primitives.d.ts.map +1 -0
  54. package/lib/messages/primitives.js +138 -0
  55. package/lib/messages/primitives.js.map +1 -0
  56. package/lib/model-server.d.ts +2 -2
  57. package/lib/model-server.d.ts.map +1 -1
  58. package/lib/rpc/bind-rpc-methods.d.ts +29 -3
  59. package/lib/rpc/bind-rpc-methods.d.ts.map +1 -1
  60. package/lib/rpc/bind-rpc-methods.js +22 -3
  61. package/lib/rpc/bind-rpc-methods.js.map +1 -1
  62. package/lib/rpc/create-rpc-proxy.d.ts +7 -0
  63. package/lib/rpc/create-rpc-proxy.d.ts.map +1 -1
  64. package/lib/rpc/create-rpc-proxy.js +6 -1
  65. package/lib/rpc/create-rpc-proxy.js.map +1 -1
  66. package/lib/testing/catalogue-audit.d.ts +80 -0
  67. package/lib/testing/catalogue-audit.d.ts.map +1 -0
  68. package/lib/testing/catalogue-audit.js +94 -0
  69. package/lib/testing/catalogue-audit.js.map +1 -0
  70. package/lib/testing/data-doubles.d.ts +11 -12
  71. package/lib/testing/data-doubles.d.ts.map +1 -1
  72. package/lib/testing/data-doubles.js +14 -5
  73. package/lib/testing/data-doubles.js.map +1 -1
  74. package/lib/testing/index.d.ts +1 -0
  75. package/lib/testing/index.d.ts.map +1 -1
  76. package/lib/testing/index.js +4 -1
  77. package/lib/testing/index.js.map +1 -1
  78. package/lib/transfer-diagnostic.d.ts +33 -0
  79. package/lib/transfer-diagnostic.d.ts.map +1 -1
  80. package/lib/transfer-diagnostic.js +23 -0
  81. package/lib/transfer-diagnostic.js.map +1 -1
  82. package/package.json +11 -2
  83. package/src/client/data-connection.ts +167 -0
  84. package/src/client/data-events.ts +24 -1
  85. package/src/client/data-port.ts +16 -22
  86. package/src/client/data-session.ts +138 -131
  87. package/src/client/index.ts +10 -7
  88. package/src/client/message-relay.ts +28 -6
  89. package/src/client/rpc-connection.ts +230 -0
  90. package/src/client-ids.ts +45 -0
  91. package/src/data/data-protocol-methods.ts +6 -3
  92. package/src/data/data-server-protocol.ts +45 -1
  93. package/src/data/events.ts +74 -3
  94. package/src/errors.ts +38 -14
  95. package/src/index.ts +5 -0
  96. package/src/messages/index.ts +35 -0
  97. package/src/messages/primitives.ts +215 -0
  98. package/src/model-server.ts +2 -2
  99. package/src/rpc/bind-rpc-methods.ts +49 -4
  100. package/src/rpc/create-rpc-proxy.ts +14 -1
  101. package/src/testing/catalogue-audit.ts +111 -0
  102. package/src/testing/data-doubles.ts +33 -17
  103. package/src/testing/index.ts +4 -1
  104. package/src/transfer-diagnostic.ts +40 -0
@@ -7,106 +7,114 @@
7
7
  * SPDX-License-Identifier: MIT
8
8
  ********************************************************************************/
9
9
 
10
- import type { MessageConnection } from 'vscode-jsonrpc';
11
- import { DATA_CLIENT_PROTOCOL_METHODS, DATA_SERVER_WIRE_PREFIX, type DataClientProtocol, type DataServerProtocol } from '../data';
12
- import { type RpcProxy, createRpcProxy } from '../rpc';
10
+ import type { DataServerProtocol, DiagnosticOf } from '../data';
11
+ import type { RpcProxy } from '../rpc';
13
12
  import type { TransferDocument } from '../transfer-document';
14
13
  import type { TransferElement } from '../transfer-element';
15
- import type { DataPort } from './data-port';
16
14
 
17
- /** Options for {@link DataSession}. */
18
- export interface DataSessionOptions {
19
- /**
20
- * Wire namespace the server is addressed under. Defaults to the
21
- * framework's {@link DATA_SERVER_WIRE_PREFIX}, which is what an unmodified
22
- * `DataServer` binds. Override only alongside the server's own
23
- * `methodNamespace` option — a mismatch turns every request into
24
- * "Unhandled method" rather than failing at wire-up.
25
- */
26
- readonly methodNamespace?: string;
27
- }
15
+ /**
16
+ * What one of `TServer`'s document methods takes, minus the `clientId` a
17
+ * {@link DataSession} stamps itself.
18
+ *
19
+ * Read off the SERVER's signature, not off the framework's own arg type: an
20
+ * adopter server widens these, and a wrapper declared against the narrow
21
+ * shape rejects the extra field on a fresh object literal, so that call
22
+ * cannot go through a session at all.
23
+ */
24
+ export type DataSessionArgs<TMethod extends (args: never) => unknown> = Omit<Parameters<TMethod>[0], 'clientId'>;
25
+
26
+ /** Open a document through a session; the session supplies `clientId`. */
27
+ export type DataSessionOpenArgs<
28
+ TTransfer extends TransferElement,
29
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
30
+ > = DataSessionArgs<TServer['openModelDocument']>;
31
+
32
+ /** Close a document through a session; the session supplies `clientId`. */
33
+ export type DataSessionCloseArgs<
34
+ TTransfer extends TransferElement,
35
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
36
+ > = DataSessionArgs<TServer['closeModelDocument']>;
37
+
38
+ /** Update a document through a session; the session supplies `clientId`. */
39
+ export type DataSessionUpdateArgs<
40
+ TTransfer extends TransferElement,
41
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
42
+ > = DataSessionArgs<TServer['updateModelDocument']>;
43
+
44
+ /** Persist a document through a session; the session supplies `clientId`. */
45
+ export type DataSessionSaveArgs<
46
+ TTransfer extends TransferElement,
47
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
48
+ > = DataSessionArgs<TServer['saveModelDocument']>;
49
+
50
+ /** The document a session hands back, carrying its server's diagnostic shape. */
51
+ export type DataSessionDocument<
52
+ TTransfer extends TransferElement,
53
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
54
+ > = TransferDocument<TTransfer, DiagnosticOf<TServer>>;
28
55
 
29
- /** One connection generation: its connection, its proxy, and its readiness. */
30
- interface Generation<TTransfer extends TransferElement> {
31
- readonly connection: Promise<MessageConnection>;
32
- readonly server: RpcProxy<DataServerProtocol<TTransfer>>;
33
- /** Set on first use; the shared readiness gate for this generation. */
34
- ready?: Promise<void>;
56
+ /**
57
+ * What a {@link DataSession} needs from the connection that minted it.
58
+ *
59
+ * Narrower than the connection itself so the dependency points one way:
60
+ * `DataConnection` constructs sessions, and nothing here imports it back.
61
+ */
62
+ export interface DataSessionHost<TTransfer extends TransferElement, TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>>> {
63
+ connected(): Promise<RpcProxy<TServer>>;
64
+ releaseSession(session: DataSession<TTransfer, TServer>): void;
35
65
  }
36
66
 
37
67
  /**
38
- * The host-invariant half of talking to the data head: everything above
39
- * {@link DataPort} that would otherwise be re-derived by every host
40
- * adapter.
68
+ * One participant on a data connection: a properties panel, a tree, a
69
+ * form editor.
41
70
  *
42
- * Three jobs, and deliberately no fourth:
71
+ * The server keys every hold and watch per `(uri, clientId)`, so the identity
72
+ * belongs to the participant rather than to the wire — several sessions share
73
+ * one connection, and two participants forced to share one identity cannot
74
+ * distinguish each other's writes from their own echoes.
43
75
  *
44
- * 1. **Build the typed proxy** over the port's connection, with the framework's
45
- * wire prefix and its drift-proof client-method allowlist.
46
- * 2. **Own the readiness gate** — `waitForReady` once per connection, shared
47
- * across concurrent callers. A socket client can connect before the
48
- * workspace walk finishes, and an early request is then answered correctly
49
- * from an empty registry, which reads as a broken project tier rather than
50
- * as a race.
51
- * 3. **Own the reconnect policy**, by dropping its connection generation when
52
- * the port disposes and building a fresh one on the next request.
76
+ * Every document operation stamps {@link clientId} itself. A caller that
77
+ * passed its own could pass another participant's, and the server would
78
+ * attribute the write and release the hold accordingly.
53
79
  *
54
- * It does **not** wrap the protocol methods; callers reach them through
55
- * {@link connected}. The one exception is {@link openDocument}, which exists
56
- * because the open/watch *order* is silently wrong the other way round — see
57
- * its own doc.
80
+ * Generic over the transfer root so this file names no grammar.
58
81
  *
59
- * Generic over the transfer root so this file names no grammar. An adopter
60
- * binds the concrete root (or the union of them, for a multi-grammar head) at
61
- * its own edge.
82
+ * `TServer` is bound to a server answering with ITS OWN diagnostic shape, read
83
+ * back off the parameter being bound. Simplifying that to
84
+ * `DataServerProtocol<TTransfer>` compiles and costs the wrappers their
85
+ * return type: every call through `TServer` would resolve against that looser
86
+ * bound, so an adopter's diagnostics would come back as the framework's and
87
+ * the document would have to be cast on the way out.
62
88
  */
63
- export class DataSession<TTransfer extends TransferElement> {
64
- protected readonly methodNamespace: string;
65
- /** The current generation, or `undefined` before the first request / after a teardown. */
66
- protected generation?: Generation<TTransfer>;
89
+ export class DataSession<
90
+ TTransfer extends TransferElement,
91
+ TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>> = DataServerProtocol<TTransfer>
92
+ > {
93
+ /** URIs this session holds open, so {@link dispose} can release exactly those. */
94
+ protected readonly openUris = new Set<string>();
67
95
  protected disposed = false;
68
- protected readonly portDisposeListener: { dispose(): void };
69
96
 
70
97
  constructor(
71
- protected readonly port: DataPort,
72
- protected readonly client: DataClientProtocol<TTransfer>,
73
- options: DataSessionOptions = {}
74
- ) {
75
- this.methodNamespace = options.methodNamespace ?? DATA_SERVER_WIRE_PREFIX;
76
- this.portDisposeListener = this.port.onDispose(() => this.dropGeneration());
77
- }
78
-
79
- /** The identity every request is made under — the port's, not a second one. */
80
- get clientId(): string {
81
- return this.port.clientId;
82
- }
98
+ readonly clientId: string,
99
+ protected readonly host: DataSessionHost<TTransfer, TServer>
100
+ ) {}
83
101
 
84
102
  /**
85
- * The connected, READY server proxy.
86
- *
87
- * Returns the proxy rather than `void` on purpose. A reconnect replaces the
88
- * proxy, so a caller that cached one from an earlier call would go on
89
- * addressing a dead connection with no error — handing it back per call
90
- * makes the stale reference unrepresentable.
91
- *
92
- * Concurrent callers share one readiness promise, so `waitForReady` is
93
- * awaited once per generation and not once per caller.
103
+ * The connected, READY server proxy, for protocol methods this session does
104
+ * not wrap — the ones carrying no `clientId`, so no identity can be got
105
+ * wrong through them.
94
106
  */
95
- async connected(): Promise<RpcProxy<DataServerProtocol<TTransfer>>> {
96
- if (this.disposed) {
97
- throw new Error('DataSession is disposed');
98
- }
99
- const generation = this.currentGeneration();
100
- if (!generation.ready) {
101
- generation.ready = this.awaitReady(generation);
102
- }
103
- await generation.ready;
104
- return generation.server;
107
+ async connected(): Promise<RpcProxy<TServer>> {
108
+ // `async` so a disposed session REJECTS rather than throwing
109
+ // synchronously: the connection's own `connected` rejects, and a caller
110
+ // reaching for `.catch` on one of them would not catch the other.
111
+ this.assertLive();
112
+ return this.host.connected();
105
113
  }
106
114
 
107
115
  /**
108
- * Open `uri` for editing and start watching it, in that order, returning
109
- * the opened snapshot.
116
+ * Open `args.uri` for editing and start watching it, in that order,
117
+ * returning the opened snapshot.
110
118
  *
111
119
  * **The order is the whole reason this method exists.**
112
120
  * `watchModelDocument` baselines its dedup fingerprint from the *current*
@@ -122,24 +130,38 @@ export class DataSession<TTransfer extends TransferElement> {
122
130
  * Validity arrives asynchronously on `onDocumentUpdated`, or synchronously
123
131
  * from `getModelDocument({ includeDiagnostics: true })`.
124
132
  */
125
- async openDocument(uri: string): Promise<TransferDocument<TTransfer>> {
133
+ async openDocument(args: DataSessionOpenArgs<TTransfer, TServer>): Promise<DataSessionDocument<TTransfer, TServer>> {
126
134
  const server = await this.connected();
127
- const document = await server.openModelDocument({ uri, clientId: this.clientId });
128
- await server.watchModelDocument({ uri, clientId: this.clientId });
135
+ const document = await server.openModelDocument({ ...args, clientId: this.clientId });
136
+ await server.watchModelDocument({ uri: args.uri, clientId: this.clientId });
137
+ this.openUris.add(args.uri);
129
138
  return document;
130
139
  }
131
140
 
132
141
  /**
133
- * Close `uri`. The server unwatches implicitly, so this is the dual of
142
+ * Close `args.uri`. The server unwatches implicitly, so this is the dual of
134
143
  * {@link openDocument} and needs no separate unwatch.
135
144
  */
136
- async closeDocument(uri: string): Promise<void> {
145
+ async closeDocument(args: DataSessionCloseArgs<TTransfer, TServer>): Promise<void> {
146
+ const server = await this.connected();
147
+ this.openUris.delete(args.uri);
148
+ await server.closeModelDocument({ ...args, clientId: this.clientId });
149
+ }
150
+
151
+ /** Write `args.model` back as this session. */
152
+ async updateDocument(args: DataSessionUpdateArgs<TTransfer, TServer>): Promise<DataSessionDocument<TTransfer, TServer>> {
137
153
  const server = await this.connected();
138
- await server.closeModelDocument({ uri, clientId: this.clientId });
154
+ return server.updateModelDocument({ ...args, clientId: this.clientId });
155
+ }
156
+
157
+ /** Persist `args.model` to disk as this session. */
158
+ async saveDocument(args: DataSessionSaveArgs<TTransfer, TServer>): Promise<DataSessionDocument<TTransfer, TServer>> {
159
+ const server = await this.connected();
160
+ return server.saveModelDocument({ ...args, clientId: this.clientId });
139
161
  }
140
162
 
141
163
  /**
142
- * Whether `event.sourceClientId` identifies this session's own write.
164
+ * Whether `sourceClientId` identifies this session's own write.
143
165
  *
144
166
  * Every watcher needs this and the check is one comparison, so getting it
145
167
  * wrong is cheap to do and expensive to find: an unfiltered echo looks
@@ -149,61 +171,46 @@ export class DataSession<TTransfer extends TransferElement> {
149
171
  return sourceClientId === this.clientId;
150
172
  }
151
173
 
152
- /** Tear down the current connection and stop tracking the port. Idempotent. */
174
+ /**
175
+ * Release this session's holds and detach it from the connection.
176
+ * Idempotent, and leaves the connection usable by its other sessions.
177
+ *
178
+ * The closes are fired without being awaited, because a `Disposable` cannot
179
+ * be: a host disposing a widget has nowhere to put the promise. A close
180
+ * that fails is no worse than the leak this exists to prevent, so the
181
+ * rejection is swallowed rather than surfaced from a teardown.
182
+ */
153
183
  dispose(): void {
154
184
  if (this.disposed) {
155
185
  return;
156
186
  }
157
187
  this.disposed = true;
158
- this.portDisposeListener.dispose();
159
- this.dropGeneration();
160
- }
161
-
162
- /** The live generation, building one if there is none. */
163
- protected currentGeneration(): Generation<TTransfer> {
164
- if (this.generation) {
165
- return this.generation;
166
- }
167
- const connection = this.port.connect();
168
- // Rejection is reported here rather than left to float: an unhandled
169
- // rejection on a connection promise is the failure mode that reads as
170
- // "the model is empty" instead of "the transport never opened".
171
- connection.catch((error: unknown) => this.port.reportError(error, 'connecting to the data server'));
172
- const server = createRpcProxy<DataServerProtocol<TTransfer>, DataClientProtocol<TTransfer>>(connection, {
173
- methodNamespace: this.methodNamespace,
174
- localTarget: this.client,
175
- localMethods: DATA_CLIENT_PROTOCOL_METHODS
176
- });
177
- this.generation = { connection, server };
178
- return this.generation;
179
- }
180
-
181
- /** Await the connection and the server's startup gate for one generation. */
182
- protected async awaitReady(generation: Generation<TTransfer>): Promise<void> {
183
- try {
184
- await generation.connection;
185
- await generation.server.waitForReady();
186
- } catch (error: unknown) {
187
- // Drop the generation so the next request retries rather than
188
- // re-awaiting a settled rejection forever.
189
- if (this.generation === generation) {
190
- this.generation = undefined;
191
- }
192
- this.port.reportError(error, 'waiting for the data server to become ready');
193
- throw error;
188
+ const uris = [...this.openUris];
189
+ this.openUris.clear();
190
+ this.host.releaseSession(this);
191
+ for (const uri of uris) {
192
+ void this.host
193
+ .connected()
194
+ .then(server => server.closeModelDocument({ uri, clientId: this.clientId }))
195
+ .catch(() => undefined);
194
196
  }
195
197
  }
196
198
 
197
199
  /**
198
- * Discard the current generation, disposing its connection if it opened.
199
- * The next {@link connected} builds a fresh one.
200
+ * Come off the connection because it is going away.
201
+ *
202
+ * Sends no close, unlike {@link dispose}: the server releases every hold on
203
+ * a connection it sees close, and the close would travel over the very
204
+ * connection being disposed.
200
205
  */
201
- protected dropGeneration(): void {
202
- const generation = this.generation;
203
- this.generation = undefined;
204
- if (!generation) {
205
- return;
206
+ detach(): void {
207
+ this.disposed = true;
208
+ this.openUris.clear();
209
+ }
210
+
211
+ protected assertLive(): void {
212
+ if (this.disposed) {
213
+ throw new Error('DataSession is disposed');
206
214
  }
207
- generation.connection.then(connection => connection.dispose()).catch(() => undefined);
208
215
  }
209
216
  }
@@ -13,8 +13,9 @@
13
13
  *
14
14
  * Where `./data` is the wire *contract* and `./rpc` is the machinery that lowers
15
15
  * it onto a connection, this is what a client wraps around both: the seam a host
16
- * fills in (`DataPort`), the lifecycle above it (`DataSession` —
17
- * readiness gate, open/watch ordering, echo recognition, reconnect), the inbound
16
+ * fills in (`DataPort`), the connection above it (`DataConnection` — readiness
17
+ * gate and reconnect), the participants on that connection (`DataSession` —
18
+ * identity, open/watch ordering, echo recognition), the inbound
18
19
  * fan-out (`DataEvents`), and the two halves of the hop for hosts whose
19
20
  * client cannot hold a socket — `createPostMessageTransport` on the client
20
21
  * side and `relayToPostMessageChannel` on the side that does hold it.
@@ -26,15 +27,17 @@
26
27
  * carries the entries.
27
28
  *
28
29
  * The Theia-specific mounting of the same contract lives in
29
- * `@hydranium/data-client-theia`: its `AbstractDataServiceFrontend` solves the
30
- * same problem against Theia's channel transport, and its `EmitterDataClient`
31
- * is the Theia-bound counterpart of `DataEvents`. Prefer this tier for
32
- * anything new, and reach for the Theia package only for what genuinely needs
33
- * Theia DI.
30
+ * `@hydranium/data-client-theia`, and is now only the TRANSPORT: its
31
+ * `ChannelDataPort` fills the `DataPort` seam over a Theia channel, and its
32
+ * `EmitterDataClient` is the Theia-bound counterpart of `DataEvents`.
33
+ * Everything above the port is here, so a Theia frontend and a browser page
34
+ * differ by which port they construct and nothing else.
34
35
  */
35
36
 
37
+ export * from './data-connection';
36
38
  export * from './data-events';
37
39
  export * from './data-port';
38
40
  export * from './data-session';
39
41
  export * from './message-relay';
40
42
  export * from './post-message-transport';
43
+ export * from './rpc-connection';
@@ -8,8 +8,29 @@
8
8
  ********************************************************************************/
9
9
 
10
10
  import { Emitter, type Disposable, type Event, type Message, type MessageReader, type MessageWriter } from 'vscode-jsonrpc';
11
+ import { defineMessage, describeError, resolve, type ResolvedMessage } from '../messages/primitives';
11
12
  import type { PostMessageChannel } from './post-message-transport';
12
13
 
14
+ export const RELAY_TRANSPORT_OPEN_FAILED = defineMessage(
15
+ 'hydranium/protocol/relay-transport-open-failed',
16
+ 'Could not open the transport to relay: {detail}'
17
+ );
18
+
19
+ export const RELAY_TRANSPORT_READ_FAILED = defineMessage(
20
+ 'hydranium/protocol/relay-transport-read-failed',
21
+ 'Could not read from the relayed transport: {detail}'
22
+ );
23
+
24
+ export const RELAY_TRANSPORT_WRITE_FAILED = defineMessage(
25
+ 'hydranium/protocol/relay-transport-write-failed',
26
+ 'Could not write to the relayed transport: {detail}'
27
+ );
28
+
29
+ export const RELAY_REPLAY_FAILED = defineMessage(
30
+ 'hydranium/protocol/relay-replay-failed',
31
+ 'Could not replay a buffered message to the relayed transport: {detail}'
32
+ );
33
+
13
34
  /**
14
35
  * The framed side of a relay: the reader/writer pair over whatever transport the
15
36
  * host actually holds — a TCP socket to the data-server, a child process' stdio,
@@ -30,13 +51,14 @@ export interface RelayTransport {
30
51
  export interface MessageRelayOptions {
31
52
  /**
32
53
  * Surface a failure the way the host does. Same contract as
33
- * `DataPort.reportError`: `context` names what was being attempted.
54
+ * `DataPort.reportError`: `reported` is a complete sentence plus the identity
55
+ * needed to render it in another language.
34
56
  *
35
57
  * A relay has no other way to report — it sits between two transports and
36
58
  * owns neither, so a swallowed error here presents as a form that never
37
59
  * populates.
38
60
  */
39
- readonly reportError?: (error: unknown, context: string) => void;
61
+ readonly reportError?: (error: unknown, reported: ResolvedMessage) => void;
40
62
  }
41
63
 
42
64
  /** A live relay. Dispose to tear both directions down. */
@@ -143,7 +165,7 @@ export function relayToPostMessageChannel(
143
165
  bufferSubscription?.dispose();
144
166
  bufferSubscription = undefined;
145
167
  buffered.length = 0;
146
- options.reportError?.(error, 'opening the transport to relay');
168
+ options.reportError?.(error, resolve(RELAY_TRANSPORT_OPEN_FAILED, { detail: describeError(error) }));
147
169
  closeFramedSide();
148
170
  return false;
149
171
  }
@@ -166,12 +188,12 @@ export function relayToPostMessageChannel(
166
188
  opened.reader.listen(message => channel.post(message)),
167
189
  opened.reader.onClose(() => closeFramedSide()),
168
190
  opened.reader.onError(error => {
169
- options.reportError?.(error, 'reading from the relayed transport');
191
+ options.reportError?.(error, resolve(RELAY_TRANSPORT_READ_FAILED, { detail: describeError(error) }));
170
192
  closeFramedSide();
171
193
  }),
172
194
  channel.onMessage(message => {
173
195
  void opened.writer.write(message).catch((error: unknown) => {
174
- options.reportError?.(error, 'writing to the relayed transport');
196
+ options.reportError?.(error, resolve(RELAY_TRANSPORT_WRITE_FAILED, { detail: describeError(error) }));
175
197
  });
176
198
  })
177
199
  );
@@ -183,7 +205,7 @@ export function relayToPostMessageChannel(
183
205
 
184
206
  for (const message of buffered) {
185
207
  void opened.writer.write(message).catch((error: unknown) => {
186
- options.reportError?.(error, 'replaying a buffered message to the relayed transport');
208
+ options.reportError?.(error, resolve(RELAY_REPLAY_FAILED, { detail: describeError(error) }));
187
209
  });
188
210
  }
189
211
  buffered.length = 0;