@7365admin1/core 3.52.3-staging.243 → 3.52.3-staging.245

package/.changeset/bulletin-board-create-rollback.md

@@ -0,0 +1,16 @@
+---
+"@7365admin1/core": patch
+---
+
+Stop silently discarding a bulletin whose recipients include a service app with no users.
+
+`POST /api/bulletin-boards` inserts the announcement inside a Mongo transaction and then
+notifies each recipient group. The five per-service-app blocks each carried a bare `return;` for
+"this site has no id" and "this app has no registered users". Those returns left the enclosing
+`try` before `commitTransaction()`, so the session was ended with the transaction still open and
+the announcement was rolled back — while the controller still answered `201 Created`. Selecting
+Cleaning, M&E, Pest Control, Landscaping or Pool Maintenance at an estate with no users of that
+app therefore made the announcement vanish with no error anywhere.
+
+The five blocks are now one loop over a recipient-to-app-slug map, and a missing push audience
+skips one notification instead of ending the request. Same apps, same order, same payloads.

package/.changeset/visitor-invite-type-default.md

@@ -0,0 +1,12 @@
+---
+"@7365admin1/core": patch
+---
+
+Default the visitor-invite `type` to `guest` so already-installed resident app builds can invite again.
+
+`POST /api/visitor-transactions/invite/:inviterId` made `type` a required field when the
+contractor invite was added. Every resident app build already in the stores sends no `type`, so
+those users get a 400 — `"type" is required` — on a form that has no Type field. `type` now
+defaults to `guest`, which is exactly what the endpoint did before the contractor work.
+Contractor invites are unchanged: `contractorType` is still required when `type` is `contractor`,
+and an unrecognised `type` is still refused.

package/dist/index.d.ts

@@ -6487,7 +6487,7 @@ declare function useBulletinBoardRepo(): {
 };
 
 declare function useBulletinBoardService(): {
-    add: (value: TBulletinBoard) => Promise<"Successfully added bulletin board." | undefined>;
+    add: (value: TBulletinBoard) => Promise<string>;
     updateBulletinBoardById: (id: string | ObjectId, value: Partial<TBulletinBoard>) => Promise<string>;
     processExpiredBulletinBoards: () => Promise<void>;
     processUpcomingBulletinBoards: () => Promise<void>;