@7365admin1/core 3.32.2-staging.82 → 3.32.2-staging.83

package/.changeset/service-provider-invite-pending-check.md

@@ -0,0 +1,17 @@
+---
+"@7365admin1/core": patch
+---
+
+Make the "an invitation is already waiting" check actually find the invitation
+
+The duplicate-invitation guard added with the existing-provider invite fix never
+fired. Invitations are written with `metadata.siteId` as an ObjectId, but the
+lookup searched for the site id as the plain string it arrived as on the request,
+and MongoDB does not treat the two as equal. The query therefore always came back
+empty: a property manager could send the same service provider a second, third
+and fourth invitation for the same site while the first was still valid, and each
+one produced another email and another pending row for them to chase.
+
+The lookup now matches either form, so older records that hold the string are
+still found. Nothing else changes: the refusal message and the status code are
+the ones already shipped.

package/dist/index.js

@@ -12480,6 +12480,11 @@ function useVerificationRepoV2() {
     }
   }
   async function getPendingServiceProviderInvite(email, siteId) {
+    const site = [siteId];
+    try {
+      site.push(new import_mongodb19.ObjectId(siteId));
+    } catch {
+    }
     try {
       return await collection.findOne(
         {
@@ -12491,7 +12496,7 @@ function useVerificationRepoV2() {
               "service-provider-create-org" /* SERVICE_PROVIDER_CREATE_ORG */
             ]
           },
-          "metadata.siteId": siteId,
+          "metadata.siteId": { $in: site },
           expireAt: { $gt: (/* @__PURE__ */ new Date()).toISOString() }
         },
         { sort: { createdAt: -1 } }