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

package/components/VisitorManagement.vue

@@ -2034,15 +2034,27 @@ const selectedVisitorObject = computed<Record<string, any>>(() => {
   ];
   includedKeys.unshift(...(typeFieldMap[type] ?? []));
 
-  let locationString = "N/A";
-
-  if (obj?.block?.name || obj?.level?.name || obj?.unitName) {
-    locationString = `${obj.block?.name} / ${obj.level?.name} / ${obj.unitName}`;
-  } else if (obj?.block?.name) {
-    locationString = obj.block?.name;
-  } else {
-    locationString = "N/A";
-  }
+  /**
+   * V-07: THE DETAIL DIALOG PRINTED `undefined / undefined / 12-34`.
+   *
+   * The guard was an OR over the three parts, but the string interpolated all
+   * THREE unconditionally - so a visitor recorded against a unit with no block
+   * and no level (every walk-in registered from the unit number alone) got the
+   * word `undefined` twice, joined by the separators, in front of a perfectly
+   * good unit. The `else if (block)` branch below it could never run: the OR
+   * above had already matched on the same block.
+   *
+   * Only the parts that EXIST are joined now, which is the same rule
+   * `useSecurityUtils().formatLocation` already applies everywhere else, so a
+   * full location still reads `Block A / Level 12 / 12-34` exactly as before
+   * and a partial one reads `12-34` instead of two undefineds.
+   */
+  const locationParts = [obj?.block?.name, obj?.level?.name, obj?.unitName]
+    .filter((part) => part !== null && part !== undefined && part !== "");
+
+  const locationString = locationParts.length
+    ? locationParts.join(" / ")
+    : "N/A";
 
   return {
     ...Object.fromEntries(

package/package.json

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