@7365admin1/layer-common 4.2.9 → 4.2.10

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @iservice365/layer-common
 
+## 4.2.10
+
+### Patch Changes
+
+- 66a947b: Add the front-end half of facility restore: `useFacility` now forwards the
+  allow-listed `status` filter to `POST /api/facilities/search/v1` (omitted
+  entirely when a caller does not ask for it, so no existing list changes) and
+  exposes `restoreFacility`, which calls the `PATCH /api/facilities/restore/v1`
+  route already live in API-core.
+
 ## 4.2.9
 
 ### Patch Changes
@@ -544,11 +554,11 @@
   `utils/console-tier.ts` + `composables/useConsoleTier.ts` mirror the server's
   own rule from two endpoints the console already calls, unprojected:
 
-                                  GET /api/members/user/:user/app/admin    the Seven365 staff membership
-                                  GET /api/roles/id/:role                  that membership's role document
+                                    GET /api/members/user/:user/app/admin    the Seven365 staff membership
+                                    GET /api/roles/id/:role                  that membership's role document
 
-                                  owner  = member.type === "admin" && role.type === "admin" && role.default === true
-                                  staff  = member.type === "admin" && role.type === "admin"
+                                    owner  = member.type === "admin" && role.type === "admin" && role.default === true
+                                    staff  = member.type === "admin" && role.type === "admin"
 
   `role.default` is the marker because it is the only property of a platform
   staff role no API caller can set - `role.controller.ts` validates create and

package/composables/useFacility.ts

@@ -317,6 +317,15 @@ export default function usetFacility() {
     }
   }
 
+  /**
+   * `status` is the "Show deleted" switch.
+   *
+   * Omitted, the server keeps its existing default of active-only, which is
+   * what every caller sends today (none send it at all), so no list changes
+   * unless a caller asks for the other one. The server allow-lists it to
+   * exactly `active` / `deleted`, so this is a passthrough of two words and
+   * not of free text.
+   */
   async function getFacilitiesByPageSearch({
     page = 1,
     search = "",
@@ -324,6 +333,7 @@ export default function usetFacility() {
     sites = [],
     _id = "",
     userType,
+    status,
   }: {
     _id?: string;
     page?: number;
@@ -331,6 +341,7 @@ export default function usetFacility() {
     sites?: string[];
     limit?: number;
     userType?: string;
+    status?: "active" | "deleted";
   }) {
     return useNuxtApp().$api("/api/facilities/search/v1", {
       method: "POST",
@@ -341,6 +352,7 @@ export default function usetFacility() {
         sites,
         _id,
         userType,
+        ...(status ? { status } : {}),
       },
     });
   }
@@ -443,6 +455,33 @@ export default function usetFacility() {
     });
   }
 
+  /**
+   * The way back from `deleteFacility`.
+   *
+   * Same verb, same two query parameters, same shape — the server gates the
+   * restore exactly as it gates the delete (`requireAuth` +
+   * `requireSiteAccess(req.query.site)`), so anyone who could delete a facility
+   * can undo it and nobody else. `restoreFacilityById` matches on
+   * `{_id, site, status: "deleted"}`, so restoring something already active is
+   * a no-op rather than a write.
+   */
+  async function restoreFacility({
+    _id,
+    site,
+    updatedBy,
+  }: {
+    _id?: string;
+    site?: string;
+    updatedBy?: string;
+  }) {
+    return useNuxtApp().$api(`/api/facilities/restore/v1?_id=${_id}&site=${site}`, {
+      method: "PATCH",
+      query: {
+        updatedBy,
+      },
+    });
+  }
+
   function setFacility(data?: TFacility) {
     facility.value = new MFacility(data);
   }
@@ -679,6 +718,7 @@ export default function usetFacility() {
     affectedBookingsTab,
     cancelFacilityBooking,
     deleteFacility,
+    restoreFacility,
     bookingFeeTaxPercentage,
     bookingCurrencySymbol,
     bookingCurrencyType,

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.2.9",
+  "version": "4.2.10",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",