doover-js 0.5.0 → 0.5.2
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/apis/agents-api.d.ts +9 -0
- package/dist/types/openapi.d.ts +25 -1
- package/package.json +1 -1
|
@@ -2,6 +2,15 @@ import type { AgentAggregate, BatchMessagesResponse } from "../types/openapi";
|
|
|
2
2
|
import type { RestClient } from "../http/rest-client";
|
|
3
3
|
export interface MultiAgentMessagesParams {
|
|
4
4
|
agent_id: string[];
|
|
5
|
+
/**
|
|
6
|
+
* Per-agent `before` cursors, parallel to `agent_id`. When set, must
|
|
7
|
+
* be the same length as `agent_id`; each agent then uses its own
|
|
8
|
+
* cursor as the upper bound instead of the global `before`. This is
|
|
9
|
+
* how paginating clients should resume from a previous response's
|
|
10
|
+
* `next_cursors` map — each agent paginates independently with no
|
|
11
|
+
* inter-agent "watermark retain".
|
|
12
|
+
*/
|
|
13
|
+
agent_before?: string[];
|
|
5
14
|
before?: string;
|
|
6
15
|
after?: string;
|
|
7
16
|
limit?: number;
|
package/dist/types/openapi.d.ts
CHANGED
|
@@ -3,7 +3,31 @@ export type { AgentAggregate, AgentPermission, Alarm, Aggregate, Channel, Connec
|
|
|
3
3
|
export interface BatchMessagesResponse {
|
|
4
4
|
results: MessageStructure[];
|
|
5
5
|
count: number;
|
|
6
|
-
|
|
6
|
+
/**
|
|
7
|
+
* Per-agent resume cursors. Any agent whose fetch hit the per-agent
|
|
8
|
+
* limit before draining the window maps to the oldest snowflake we
|
|
9
|
+
* did return for it. Pass these back as `agent_before` (parallel to
|
|
10
|
+
* `agent_id`) on the next call to continue paginating each agent
|
|
11
|
+
* independently. Empty (or missing, on older servers) when the
|
|
12
|
+
* window is fully drained.
|
|
13
|
+
*
|
|
14
|
+
* This is the canonical pagination signal — `next` and
|
|
15
|
+
* `at_limit_agent_ids` are kept populated for back-compat with
|
|
16
|
+
* pre-`next_cursors` clients.
|
|
17
|
+
*/
|
|
18
|
+
next_cursors?: Record<string, string>;
|
|
19
|
+
/**
|
|
20
|
+
* Legacy single-cursor pagination signal — the most-recent (highest
|
|
21
|
+
* snowflake id) oldest-cursor across at-limit agents. Clients
|
|
22
|
+
* paginating with a single global `before` should pass this back;
|
|
23
|
+
* prefer `next_cursors` + `agent_before` for new code.
|
|
24
|
+
*/
|
|
25
|
+
next?: string | null;
|
|
26
|
+
/**
|
|
27
|
+
* Legacy: agent ids with possibly-more older messages — equivalent to
|
|
28
|
+
* `Object.keys(next_cursors)`. Prefer `next_cursors` for new code.
|
|
29
|
+
*/
|
|
30
|
+
at_limit_agent_ids?: string[];
|
|
7
31
|
}
|
|
8
32
|
export interface BatchAggregatesResponse {
|
|
9
33
|
results: AgentAggregate[];
|