@7365admin1/layer-common 4.97.1-staging.584 → 4.97.1-staging.585

package/components/AccessCardQrTagging.vue

@@ -9,7 +9,10 @@
         tokens. Same three clicks, same `disabled` rules; the primary action
         sits rightmost, where the design puts it.
       -->
-      <PageHeader title="QR Tagging">
+      <PageHeader
+        title="QR Tagging"
+        subtitle="Make a printable QR sticker for each access card, so a card can be identified by scanning its QR. Tick the cards, then Generate QR Code; Print QR Code prints the ones that already have a QR."
+      >
         <template #actions>
           <AppButton
             variant="ghost"
@@ -26,6 +29,7 @@
             Print QR Code
           </AppButton>
           <AppButton
+            v-if="canGenerate"
             :disabled="!qrCodeAccessCards.length"
             @click="generateQrCodes"
           >
@@ -186,6 +190,12 @@ const props = defineProps({
     type: Boolean,
     default: false,
   },
+  // Generate writes a QR tag onto each selected card. Default true keeps
+  // every consumer that does not pass it unchanged.
+  canGenerate: {
+    type: Boolean,
+    default: true,
+  },
 });
 
 const tableHeaders = [

package/components/BuildingManagement/buildings.vue

@@ -117,12 +117,12 @@
     <v-dialog v-model="confirmDialog" :loading="deleteLoading" width="450" persistent>
       <v-card width="100%">
         <v-toolbar density="compact" class="pl-4">
-          <span class="font-weight-medium text-h5">Delete Building</span>
+          <span class="font-weight-medium text-h5">Delete Block</span>
         </v-toolbar>
 
         <v-card-text>
           <p class="text-subtitle-2 text-center">
-            Are you sure you want to delete this building? This action cannot be
+            Are you sure you want to delete this block? This action cannot be
             undone.
           </p>
 
@@ -288,14 +288,14 @@ function tableRowClickHandler(_: any, data: any) {
 function successCreate() {
   createDialog.value = false;
   getBuildings();
-  showMessage("Building created successfully!", "success");
+  showMessage("Block created successfully!", "success");
 }
 
 function successUpdate() {
   editDialog.value = false;
   previewDialog.value = false;
   getBuildings();
-  showMessage("Building updated successfully!", "success");
+  showMessage("Block updated successfully!", "success");
 }
 
 function openEditDialog() {
@@ -327,7 +327,7 @@ async function handleDeleteBuilding() {
     previewDialog.value = false
   } catch (error: any) {
     message.value =
-      error?.response?._data?.message || "Failed to delete region";
+      error?.response?._data?.message || "Failed to delete block";
   } finally {
     deleteLoading.value = false;
   }

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.97.1-staging.584",
+  "version": "4.97.1-staging.585",
   "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.",