@7365admin1/layer-common 4.97.1-staging.598 → 4.97.1-staging.599

package/components/Chat/Message.vue

@@ -8,6 +8,11 @@
       <h3 class="screen-card-title">
         {{ type === "workOrder" ? "Work Order" : "Feedback" }} Chat
       </h3>
+      <div class="text-body-2 text-medium-emphasis">
+        Between the Managing Agent and the service provider on this
+        {{ type === "workOrder" ? "work order" : "feedback" }}. The other side
+        is notified of each new message.
+      </div>
     </div>
 
     <v-sheet
@@ -23,7 +28,7 @@
         v-else-if="!days.length"
         class="text-center text-medium-emphasis py-6"
       >
-        No messages yet
+        No messages yet. Send a message or a photo below to start.
       </div>
 
       <template v-for="group in days" :key="group.day">
@@ -48,7 +53,7 @@
                 :message="msg.comment"
                 :timestamp="formatTime(msg.createdAt)"
                 :senderName="isMine(msg) ? 'You' : msg.createdByName || 'User'"
-                :role="msg.createdByType"
+                :role="senderSideLabel(msg.createdByMemberType) || msg.createdByType"
                 :attachments="msg.attachments"
                 :avatarId="msg.createdByProfile"
                 @preview="openPreview"
@@ -186,7 +191,7 @@
 </template>
 
 <script setup lang="ts">
-import { groupChatByDay } from "../../utils/chat-sender.ts";
+import { groupChatByDay, senderSideLabel } from "../../utils/chat-sender.ts";
 
 /**
  * The comment thread under a feedback or a work order.

package/package.json

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

package/types/comment.d.ts

@@ -9,6 +9,8 @@ declare type TCommentChat = {
   updatedAt?: string;
   createdByName?: string;
   createdByType?: string;
+  /** The sender's membership type at the site, stamped by the server (e.g. "property_management_agency"). */
+  createdByMemberType?: string;
   /** The sender's avatar file id. The API has always returned it. */
   createdByProfile?: string;
   justify?: string;

package/utils/chat-sender.ts

@@ -25,6 +25,23 @@ export function formatSenderRole(
     .join(" ");
 }
 
+/**
+ * Which side of the conversation wrote a message, from the membership type the
+ * server stamps on it (`createdByMemberType`): "Managing Agent", "Service
+ * Provider", "Security" or "Resident"; "" when the type says nothing useful
+ * (the panel then falls back to `formatSenderRole`). Kept in step with
+ * `senderSide` in the mobile apps.
+ */
+export function senderSideLabel(memberType: string | undefined | null): string {
+  const t = (memberType ?? "").trim().toLowerCase();
+  if (!t) return "";
+  if (t === "property_management_agency") return "Managing Agent";
+  if (t === "security_agency") return "Security";
+  if (t === "resident") return "Resident";
+  if (t.endsWith("_services") || t === "service-provider" || t === "service_provider") return "Service Provider";
+  return "";
+}
+
 /**
  * A thread already in reading order (oldest first, as `useComment.setComments`
  * sorts it), split into one group per day so the panel can draw a single day