Address issue where causing NaN chunks

Where there are 0 existing CGPS List Chunks, but other existing list(s), the calculation for the next list number would result in NaN
mrrfv · Jan 2, 2025 · 5f7fb1a · 5f7fb1a
1 parent 8da6ca6
commit 5f7fb1a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/lib/api.js b/lib/api.js
@@ -165,7 +165,7 @@ export const synchronizeZeroTrustLists = async (items) => {
   // Are there any more appends remaining?
   if (toAdd.length) {
     // We'll need to create new list(s)
-    const nextListNumber = Math.max(cgpsLists.map(list => parseInt(list.name.replace('CGPS List - Chunk ', '')))) + 1;
+    const nextListNumber = Math.max(cgpsLists.map(list => parseInt(list.name.replace('CGPS List - Chunk ', ''))).filter(x => !isNaN(x))) + 1;
     await createZeroTrustListsOneByOne(toAdd, nextListNumber);
   }
 };