@7365admin1/layer-common 3.2.2-staging.190 → 3.2.2-staging.191

package/components/DashboardMain.vue

@@ -724,7 +724,7 @@
       <v-col v-if="isWidgetVisible('todayAttentions')" cols="12" lg="6">
         <div class="dashboard-card dashboard-panel figma-panel">
           <div class="figma-panel-header">
-            <h2>Today's Attentions</h2>
+            <h2>Needs Attention</h2>
           </div>
           <div class="figma-panel-body">
             <div v-if="todayAttentions.length" class="figma-list">
@@ -2084,9 +2084,9 @@ const customizeWidgets = computed(() => {
       },
       {
         key: "todayAttentions",
-        title: "Today's Attentions",
+        title: "Needs Attention",
         description:
-          "Items that require review overdue, pending, or unacknowledged.",
+          "Everything still pending or unacknowledged, not only today's.",
       },
       {
         key: "workOrderStatus",
@@ -2487,6 +2487,12 @@ const dashboardTitle = computed(() => {
   return `${getServiceDisplayName(props.serviceType || appName)} - Dashboard`;
 });
 
+const taskScheduleTitle = computed(() => {
+  if (selectedRange.value === "This Month") return "This Month's Task Schedule";
+  if (selectedRange.value === "This Week") return "This Week's Task Schedule";
+  return "Today's Task Schedule";
+});
+
 // ─── Primary list / staff config ─────────────────────────────────────────────
 
 const primaryListConfig = computed(() =>
@@ -2497,7 +2503,11 @@ const primaryListConfig = computed(() =>
         keys: ["activePatrolItems", "patrolItems"],
       }
     : {
-        title: "Today's Task Schedule",
+        // The endpoint behind this panel takes the selected period
+        // (`getServiceTodayTaskSchedule` -> `getDateRange(period)`), so on the
+        // Week or Month range the list was a week's or a month's work under a
+        // heading that said "Today's".
+        title: taskScheduleTitle.value,
         route: "scheduleTask",
         keys: [
           "taskScheduleItems",
@@ -2780,7 +2790,7 @@ const printTableSections = computed<PrintTableSection[]>(() => {
       },
       {
         key: "todayAttentions",
-        title: "Today's Attentions",
+        title: "Needs Attention",
         columns: [
           { key: "title", label: "Attention", width: "40%", strong: true },
           { key: "subtitle", label: "Details / Subtitle", width: "60%" },
@@ -3727,7 +3737,7 @@ async function exportDashboard(format: "PDF" | "Word") {
         }
         wordHtml += `</tbody></table>`;
 
-        wordHtml += `<div class="section-title">Today's Attentions</div>`;
+        wordHtml += `<div class="section-title">Needs Attention</div>`;
         wordHtml += `<table class="data-table">`;
         wordHtml += `<thead><tr><th>Attention</th><th>Details / Subtitle</th></tr></thead><tbody>`;
         if (todayAttentions.value.length > 0) {

package/package.json

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