@gvnrdao/dh-sdk 0.0.332 → 0.0.334

package/dist/graphs/diamond-hands.d.ts

@@ -86,6 +86,43 @@ export interface UserRateLimitData {
     nextResetBlock: string;
     lastUpdated: string;
 }
+/**
+ * Raw shape of the `GetLoanEvents` document response.
+ *
+ * Module-scoped so BOTH event paths can share one transform: the per-position
+ * `getLoanEvents` fetch, and the wallet-collapsed `GetWalletLoanEvents` fetch that
+ * reshapes each position into this same form. Sharing the transform is the point —
+ * two hand-written mappings for the same entity WILL drift, which is the exact class
+ * of bug that took the PSM reads down for 17 days.
+ */
+/**
+ * True when the caller narrowed the event set in ANY way.
+ *
+ * Deliberately conservative: every field counts, including `limit`/`orderDirection` even
+ * at their default values. A false negative here would send a narrowed request down the
+ * collapsed path and silently return unfiltered data; a false positive only costs the old
+ * fan-out. Wrong-but-slow beats wrong-but-wrong.
+ */
+/**
+ * Narrow an assembled `LoanEvents` in memory.
+ *
+ * The proxy allowlists GraphQL documents by hash, so a filtered request cannot be
+ * expressed as a narrower document — see the note in `getLoanEvents`. The request
+ * is therefore always the full shape and the narrowing happens here.
+ *
+ * `totalEvents` is RECOMPUTED from what survives, so it describes the returned
+ * set rather than what the subgraph held. A caller that filtered to
+ * `positionCreated` and still saw `totalEvents: 12` would reasonably assume the
+ * filter had not applied.
+ */
+export declare function applyLoanEventsFilter(events: LoanEvents, opts: {
+    wantsEvent: (kind: NonNullable<LoanEventsFilter["eventTypes"]>[number]) => boolean;
+    fromTimestamp?: string;
+    toTimestamp?: string;
+    fromBlock?: string;
+    toBlock?: string;
+    limit: number;
+}): LoanEvents;
 export interface LoanEventsQueryResponse {
     position: {
         id: string;