feat: invalidate cache on signature request changes

Without this patch adding a new signature request to the database
doesn't invalidate the cache right away. This needs to be triggered
manually.

Author: pheuberger

src/client/supabase.ts

@@ -204,6 +204,21 @@ const handleChangeOrders = (
   }
 };
 
+/* eslint-disable  @typescript-eslint/no-explicit-any */
+const handleChangeSignatureRequests = (
+  payload: RealtimePostgresChangesPayload<{ [key: string]: any }>,
+) => {
+  switch (payload.eventType) {
+    case "INSERT":
+    case "UPDATE":
+    case "DELETE":
+      cache.invalidate([{ typename: "SignatureRequest" }]);
+      break;
+    default:
+      break;
+  }
+};
+
 supabaseCaching
   .channel("schema-db-changes")
   .on(
@@ -402,4 +417,13 @@ supabaseData
     },
     (payload) => handleChangeOrders(payload),
   )
+  .on(
+    "postgres_changes",
+    {
+      event: "*",
+      schema: "public",
+      table: "signature_requests",
+    },
+    (payload) => handleChangeSignatureRequests(payload),
+  )
   .subscribe();