@dudousxd/nestjs-durable-dashboard 0.46.0 → 0.47.0

package/dist/server/index.d.cts

@@ -282,7 +282,9 @@ declare class DurableApiController {
      * so a picker never offers a value whose result set is empty.
      *
      * `limit` matters rather than being a nicety — tag and attribute cardinality grows with the data
-     * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing.
+     * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing. `offset` and
+     * `search` are what make that bound livable: a picker pages as it scrolls and narrows as the
+     * operator types, both server-side, so a value outside the first page is still reachable.
      */
     values(query: Record<string, unknown>): Promise<_dudousxd_nestjs_filter.GroupByCountResult>;
     /** Prometheus-text metrics (runs/steps by outcome, per-workflow counts) for a scrape. */

package/dist/server/index.d.ts

@@ -282,7 +282,9 @@ declare class DurableApiController {
      * so a picker never offers a value whose result set is empty.
      *
      * `limit` matters rather than being a nicety — tag and attribute cardinality grows with the data
-     * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing.
+     * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing. `offset` and
+     * `search` are what make that bound livable: a picker pages as it scrolls and narrows as the
+     * operator types, both server-side, so a value outside the first page is still reachable.
      */
     values(query: Record<string, unknown>): Promise<_dudousxd_nestjs_filter.GroupByCountResult>;
     /** Prometheus-text metrics (runs/steps by outcome, per-workflow counts) for a scrape. */

package/dist/server/index.js

@@ -625,7 +625,9 @@ var RunQueryAdapter = class {
   /**
   * The distinct values of one field over the runs the active predicates select — the console's
   * pickers. `limit` is honoured because it has to be: tag and search-attribute cardinality grows
-  * with the data, so the unbounded answer is a listing rather than an aggregate.
+  * with the data, so the unbounded answer is a listing rather than an aggregate. `offset` and
+  * `search` are what keep that bound from becoming a ceiling — the picker pages as it scrolls and
+  * narrows as the operator types, both against the whole matching set rather than the fetched page.
   */
   async groupByCount(qb, field, entity, opts) {
     this.assertDurableRun(entity);
@@ -640,7 +642,13 @@ var RunQueryAdapter = class {
       throw new BadRequestException(`The durable run list cannot enumerate values of \`${field}\`.`);
     }
     const rows = await this.gateway.runValueFacets(axis, this.draft(qb).facetQuery(), {
-      limit: opts?.limit ?? RUN_VALUE_FACET_LIMIT
+      limit: opts?.limit ?? RUN_VALUE_FACET_LIMIT,
+      ...opts?.offset !== void 0 && {
+        offset: opts.offset
+      },
+      ...opts?.search !== void 0 && {
+        search: opts.search
+      }
     });
     return rows.map((row) => ({
       value: row.value,
@@ -942,7 +950,9 @@ var DurableApiController = class {
   * so a picker never offers a value whose result set is empty.
   *
   * `limit` matters rather than being a nicety — tag and attribute cardinality grows with the data
-  * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing.
+  * (a `singleton:<key>` tag is minted per key), so the unbounded answer is a listing. `offset` and
+  * `search` are what make that bound livable: a picker pages as it scrolls and narrows as the
+  * operator types, both server-side, so a value outside the first page is still reachable.
   */
   values(query) {
     return this.runner.groupByCount(DurableRun, query, {