@pythia-software/query-table-core 0.9.2 → 0.9.4

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 (3) hide show
  1. package/dist/index.d.ts +4 -3
  2. package/dist/index.js.map +1 -1
  3. package/package.json +2 -2
package/dist/index.d.ts CHANGED
@@ -1372,9 +1372,10 @@ interface Transport<Row = any> {
1372
1372
  fetchRowsV2?(query: ServerQueryV2, signal?: AbortSignal): Promise<FetchRowsResultV2<Row>>;
1373
1373
  metricCapabilities?: MetricCapabilities;
1374
1374
  fetchMetrics?(query: MetricQuery, signal?: AbortSignal): Promise<AggregationResult>;
1375
- /** Run a server query. The only required method — a purely client-side table
1376
- * can omit a Transport entirely and rely on applyQuery over local rows. */
1377
- fetchRows(query: ServerQuery, signal?: AbortSignal): Promise<FetchRowsResult<Row>>;
1375
+ /** Legacy row execution. A remote table needs this, fetchRowsV2 with a
1376
+ * computedExecution handshake, or fetchQueryV3 with queryCapabilities.
1377
+ * Modern hosts may omit the legacy endpoint, including for draft previews. */
1378
+ fetchRows?(query: ServerQuery, signal?: AbortSignal): Promise<FetchRowsResult<Row>>;
1378
1379
  /** Distinct values for filter autocomplete. Strongly recommended: without it,
1379
1380
  * fields fall back to freeform input. The backend should match `search`
1380
1381
  * server-side (e.g. ILIKE prefix) and cap at `limit` so large domains stay