@naniteninja/dashboard-components-lib 2.4.3 → 2.4.4

package/fesm2022/naniteninja-dashboard-components-lib.mjs

@@ -8701,7 +8701,34 @@ function extractShortName(address) {
     const short = parts[0].trim();
     return short.length > 20 ? `${short.slice(0, 20)}...` : short;
 }
+/**
+ * What to show the matcher once the prospect has taken up something the matcher offered.
+ *
+ * The two routes leave the same shape behind — an accepted location and time — so the
+ * status fields alone cannot say who agreed to what. Read as though it were the other
+ * route, this one announced "Client has ACCEPTED …", which is the wrong party: on this
+ * route the client was told, not asked, and it is the prospect who accepted.
+ */
+function buildMatcherProposedText(s) {
+    const lines = [];
+    const loc = s.location?.trim() || '';
+    const timeParts = [s.time, s.day, s.date].filter((v) => v && v !== 'unknown').join(', ');
+    if (loc && (s.locationStatus === 'accepted' || s.locationStatus === 'auto_accepted')) {
+        lines.push(`Prospect ACCEPTED your location: ${loc}`);
+    }
+    if (timeParts && s.timeStatus === 'accepted') {
+        lines.push(`Prospect ACCEPTED your time: ${timeParts}`);
+    }
+    // Marked as the matcher's but nothing agreed yet — the offer is still with the prospect.
+    if (lines.length === 0) {
+        return 'Awaiting the prospect on your suggestion';
+    }
+    return lines.join(' | ');
+}
 function buildSplitSuggestionText(s) {
+    // The matcher-proposed route has its own wording and shares none of the logic below.
+    if (s.proposedBy === 'matcher')
+        return buildMatcherProposedText(s);
     const lines = [];
     const locStatus = s.locationStatus;
     const timeStatus = s.timeStatus;