@7365admin1/layer-common 4.2.9-staging.278 → 4.2.9

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # @iservice365/layer-common
 
+## 4.2.9
+
+### Patch Changes
+
+- 6047354: Visitor Management preview dialog: gate Check In on the guest's status, and rebuild the field list on the type scale.
+
+  - Check In is disabled while a guest's registration is still `pending`. The Guests row has withheld its own Checkin button for pending and rejected registrations since DV-0080, but the preview opened from that same row still offered Check In, so a guest could be checked in before anyone approved or rejected them.
+  - The Guests status is now shown as a `StatusChip`, which is what tells the reader why Check In is unavailable. Gated on the same `activeTab === 'guests' && status` the row's status column uses, so no other tab's preview gains a field.
+  - The fields were `<strong>Label:</strong> value` in a gapless `v-row` - a browser-default bold label beside an unstyled value, no token on either, rows flush against each other. The label still sits beside its value, but on `AccessCardDetailsDialog`'s type - `--fs-breadcrumb`/`--text2` for the label, `--fs-cell`/`--fw-cell`/`--text` for the value - in a fixed 116px label column so every value starts on one edge, with a `--border` hairline per row.
+  - Fixed: "Entry Image" and "Exit Image" printed as bare labels over an `AttachmentsViewer` holding `[undefined]` for every visitor without ANPR snapshots. They now render only when that snapshot exists.
+  - Fixed: both snapshot fields read `snapshotEntryImage`, so a visitor with both was shown the entry photo twice, the second time labelled "Exit Image".
+
+- c427a40: Season Pass dialog (`VehicleForm`): stop the Block/Level/Unit autocompletes from being destroyed mid-typing, and stop the Season Pass Type from being re-cased on save.
+
+  - The Block, Level and Unit autocompletes were `:key`'d to their loading flag alone, so every time a list resolved Vue destroyed and recreated the field — including while someone was typing into it, discarding the filter text and closing the open menu. The remount now also requires the field to already hold a value, which is the only case it was added for (an edit dialog showing "Loading unit..." until the real name arrives).
+  - `submit()` applied `charAt(0).toUpperCase() + slice(1).toLowerCase()` to the whole Season Pass Type, so "Resident Season Pass" was stored as "Resident season pass". The combobox does not recognise the re-cased string, registers it as a new custom type, and the chooser fills up with near-duplicate options. The value is now stored as picked, trimmed only.
+
 ## 4.2.8
 
 ### Patch Changes
@@ -527,11 +544,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/components/VehicleForm.vue

@@ -54,6 +54,21 @@
             </v-combobox>
           </v-col>
 
+          <!--
+            The `:key` remount exists for ONE case: an edit dialog opens with a
+            block/level/unit already stored, `withUnresolved` shows
+            "Loading unit..." until the list arrives, and Vuetify needs the
+            remount to swap in the real name. `&& vehicle.<field>` limits it to
+            exactly that case.
+
+            Without the guard it also fired on an EMPTY field: pick a Block, the
+            level list refetches, `levelListDataPending` flips, the key changes,
+            and Vue destroys and recreates the Level autocomplete underneath the
+            person using it - discarding whatever they had typed to filter it and
+            taking the open menu with it. That is the "eats keystrokes" half of
+            the Season Pass dialog report. An empty field has nothing unresolved
+            to redraw, so it has nothing to gain from the remount.
+          -->
           <v-col v-if="shouldShowField('block')" cols="12">
             <InputLabel class="text-capitalize" title="Block" required />
             <v-autocomplete
@@ -61,7 +76,9 @@
               :items="blockItems"
               autocomplete="off"
               :key="
-                blockListDataPending ? 'block-list-pending' : 'block-list-ready'
+                blockListDataPending && vehicle.block
+                  ? 'block-list-pending'
+                  : 'block-list-ready'
               "
               :loading="blockListDataPending"
               item-value="value"
@@ -79,7 +96,9 @@
               :items="levelItems"
               autocomplete="off"
               :key="
-                levelListDataPending ? 'level-list-pending' : 'level-list-ready'
+                levelListDataPending && vehicle.level
+                  ? 'level-list-pending'
+                  : 'level-list-ready'
               "
               :loading="levelListDataPending"
               density="comfortable"
@@ -96,7 +115,9 @@
               :items="unitItems"
               autocomplete="off"
               :key="
-                unitListDataPending ? 'unit-list-pending' : 'unit-list-ready'
+                unitListDataPending && vehicle.unit
+                  ? 'unit-list-pending'
+                  : 'unit-list-ready'
               "
               :loading="unitListDataPending"
               density="comfortable"
@@ -881,10 +902,18 @@ async function submit() {
 
   processing.value = true;
   try {
+    // Whitespace only. This used to be
+    // `charAt(0).toUpperCase() + slice(1).toLowerCase()`, which re-cased the
+    // WHOLE string: picking "Resident Season Pass" from the list saved
+    // "Resident season pass", and "VIP/Preferred Parking Pass" saved
+    // "Vip/preferred parking pass". Because the combobox adds any value it does
+    // not recognise as a new custom type, the re-cased copy came back as a
+    // SECOND entry in the list next to the original - which is how the Season
+    // Pass Type chooser stacked up near-duplicate options. The value the person
+    // picked is the value that is stored.
     const SPTVal = vehicle?.seasonPassType as string;
     if (SPTVal) {
-      vehicle.seasonPassType =
-        SPTVal?.charAt(0)?.toUpperCase() + SPTVal?.slice(1)?.toLowerCase();
+      vehicle.seasonPassType = SPTVal.trim();
     }
 
     const {

package/package.json

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