fix(batch): renable doBatchRead when sortKey and blockHeight are not …

…provided

This will at least improve the latency of full state evaluations when sortKey and blockHeight are not provided.

src/api/warp.ts

@@ -24,7 +24,7 @@ import {
 } from 'warp-contracts';
 import {
   DEFAULT_EVALUATION_OPTIONS,
-  // DEFAULT_PAGES_PER_BATCH,
+  DEFAULT_PAGES_PER_BATCH,
   allowedContractTypes,
 } from '../constants';
 import { ContractType, EvaluatedContractState } from '../types';
@@ -218,21 +218,22 @@ async function readThroughToContractState(
     ),
   });
 
-  // only use batch read if no block height provided (it does not currently support block heights)
-  const doBatchRead = !!providedSortKey || providedBlockHeight === undefined;
+  // only use batch read if no block height or sort key provided
+  const doBatchRead = !providedSortKey && !providedBlockHeight;
   logger?.debug('Evaluating contract state...', {
     contractTxId,
     cacheKey: cacheKey.toString(),
     doBatchRead, // there is a bug in warp where readStateBatch is not properly using sortKeys
     evaluationOptions,
   });
 
-  // TODO: re-enable readStateBatch after sortKey is fixed
-  const readStatePromise = contract.readState(
-    providedSortKey || providedBlockHeight,
-    undefined,
-    signal,
-  );
+  const readStatePromise = doBatchRead
+    ? contract.readStateBatch(DEFAULT_PAGES_PER_BATCH, undefined, signal)
+    : contract.readState(
+        providedSortKey || providedBlockHeight,
+        undefined,
+        signal,
+      );
 
   // set cached value for multiple requests during initial promise
   stateRequestMap.set(cacheId, readStatePromise);