@arbidocs/sdk 0.3.48 → 0.3.49
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/dist/{browser-EMgd4bP4.d.cts → browser-BJdLTFSM.d.cts} +5 -4
- package/dist/{browser-EMgd4bP4.d.ts → browser-BJdLTFSM.d.ts} +5 -4
- package/dist/browser.cjs.map +1 -1
- package/dist/browser.d.cts +1 -1
- package/dist/browser.d.ts +1 -1
- package/dist/browser.js.map +1 -1
- package/dist/index.cjs +2 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +2 -2
- package/dist/index.d.ts +2 -2
- package/dist/index.js +2 -1
- package/dist/index.js.map +1 -1
- package/package.json +2 -2
|
@@ -425,10 +425,11 @@ declare function connectWithReconnect(options: ReconnectOptions): Promise<Reconn
|
|
|
425
425
|
* Document statuses that mean processing is finished (success or otherwise).
|
|
426
426
|
*
|
|
427
427
|
* Anything in this set should cause `--watch` loops to stop tracking the doc:
|
|
428
|
-
* - `completed`
|
|
429
|
-
* - `failed`
|
|
430
|
-
* - `empty`
|
|
431
|
-
* - `
|
|
428
|
+
* - `completed` — happy path, content extracted and indexed
|
|
429
|
+
* - `failed` — processing errored
|
|
430
|
+
* - `empty` — parser found no extractable content (e.g. blank scan)
|
|
431
|
+
* - `low-content` — parser extracted only 1-2 chunks (minimal content)
|
|
432
|
+
* - `skipped` — server skipped (duplicate, unsupported, quota, etc.)
|
|
432
433
|
*
|
|
433
434
|
* Treating anything else as terminal will leave watchers hung when the parser
|
|
434
435
|
* legitimately bails out on degenerate input (we hit this on the bench script
|
|
@@ -425,10 +425,11 @@ declare function connectWithReconnect(options: ReconnectOptions): Promise<Reconn
|
|
|
425
425
|
* Document statuses that mean processing is finished (success or otherwise).
|
|
426
426
|
*
|
|
427
427
|
* Anything in this set should cause `--watch` loops to stop tracking the doc:
|
|
428
|
-
* - `completed`
|
|
429
|
-
* - `failed`
|
|
430
|
-
* - `empty`
|
|
431
|
-
* - `
|
|
428
|
+
* - `completed` — happy path, content extracted and indexed
|
|
429
|
+
* - `failed` — processing errored
|
|
430
|
+
* - `empty` — parser found no extractable content (e.g. blank scan)
|
|
431
|
+
* - `low-content` — parser extracted only 1-2 chunks (minimal content)
|
|
432
|
+
* - `skipped` — server skipped (duplicate, unsupported, quota, etc.)
|
|
432
433
|
*
|
|
433
434
|
* Treating anything else as terminal will leave watchers hung when the parser
|
|
434
435
|
* legitimately bails out on degenerate input (we hit this on the bench script
|