fix: accept exhausted WHOOP collection pages

src/__tests__/whoop/client.test.ts

@@ -232,6 +232,19 @@ describe("WHOOP v2 client", () => {
     );
   });
 
+  it("treats a live null next token as collection exhaustion", async () => {
+    vi.spyOn(globalThis, "fetch").mockResolvedValue(jsonResponse({
+      records: [SLEEP],
+      next_token: null,
+    }));
+    const client = new WhoopClient(ENV, "access");
+
+    await expect(client.getCollection("sleep")).resolves.toMatchObject({
+      nextToken: undefined,
+      records: [{ id: SLEEP.id }],
+    });
+  });
+
   it("rejects provider collection limits outside the whole-number range 1 through 25 before fetching", async () => {
     const fetchMock = vi.spyOn(globalThis, "fetch");
     const client = new WhoopClient(ENV, "access");

src/schemas/whoop.ts

@@ -105,7 +105,7 @@ export const whoopWorkoutSchema = z.object({
 
 export const whoopCollectionResponseSchema = <T extends z.ZodTypeAny>(recordSchema: T) => z.object({
   records: z.array(recordSchema),
-  next_token: z.string().optional(),
+  next_token: z.string().nullish(),
 }).passthrough();
 
 export type WhoopWebhook = z.infer<typeof whoopWebhookSchema>;

src/services/whoop/client.ts

@@ -234,7 +234,7 @@ export class WhoopClient {
         record,
         rawRecords[index],
       )) as Array<WhoopProviderRecord<WhoopCollectionRecordMap[R]>>,
-      nextToken: parsed.data.next_token,
+      nextToken: parsed.data.next_token ?? undefined,
     };
   }