@icanbwell/baileyai-chat-ui 1.0.19 → 1.0.21
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/README.md +4 -0
- package/dist/baileyai-chat-ui.cjs +3 -3
- package/dist/baileyai-chat-ui.js +645 -625
- package/dist/index.d.ts +9 -8
- package/package.json +1 -1
package/dist/index.d.ts
CHANGED
|
@@ -246,15 +246,16 @@ export declare interface BaileyChatTransport {
|
|
|
246
246
|
* error state (the partial text stays visible) instead of treating it as a finished
|
|
247
247
|
* answer. A transport that never sets it behaves exactly as before. */
|
|
248
248
|
interrupted?: boolean;
|
|
249
|
-
/** Optional. Why
|
|
250
|
-
*
|
|
251
|
-
*
|
|
252
|
-
*
|
|
253
|
-
*
|
|
254
|
-
* Hosts that ignore this field
|
|
249
|
+
/** Optional. Why the request failed without a complete answer; the type is a subset of
|
|
250
|
+
* `BaileyApiErrorKind`. `createBaileyClient` sets `'network'` (with `status: undefined`) when
|
|
251
|
+
* `fetch` rejects or the host's `getHeaders` throws, and `'timeout'` when its own idle timer
|
|
252
|
+
* fires (`status` is set, with `interrupted: true`, only if the response had begun). A
|
|
253
|
+
* `TimeoutError` the caller aborts with is still rethrown, as is any other caller abort.
|
|
254
|
+
* `errorMessage` stays a fixed string. Hosts that ignore this field see a failed or
|
|
255
|
+
* interrupted turn, where the idle timeout used to throw `TimeoutError`. */
|
|
255
256
|
errorKind?: Extract<BaileyApiErrorKind, 'network' | 'timeout'>;
|
|
256
|
-
/** Optional. The error `fetch` threw,
|
|
257
|
-
*
|
|
257
|
+
/** Optional. The error behind `errorKind`: what `fetch` threw, or the idle-timeout
|
|
258
|
+
* `TimeoutError`. Never set when `getHeaders` threw (it can carry auth detail) and never
|
|
258
259
|
* a request or response body. Browsers do not distinguish CORS, DNS or offline: all
|
|
259
260
|
* surface as a generic `TypeError`. Do not show `cause.message` to users without review,
|
|
260
261
|
* and do not log the request URL (it can carry identifiers). */
|