@memberjunction/ng-conversations 6.1.0-edge.2 → 6.1.0-edge.4

package/dist/lib/utils/date-jump.js

@@ -0,0 +1,106 @@
+/**
+ * Ceiling on older-page loads for one jump.
+ *
+ * A jump into a very old conversation would otherwise page the entire history back — the
+ * exact unbounded read windowing exists to prevent. On a miss the caller lands the user at
+ * the oldest loaded message instead, which is where paging left them anyway.
+ */
+export const DATE_JUMP_MAX_PAGES = 50;
+/** Local midnight `daysAgo` days before `now`. */
+function startOfDayBefore(now, daysAgo) {
+    const d = new Date(now.getFullYear(), now.getMonth(), now.getDate());
+    d.setDate(d.getDate() - daysAgo);
+    return d;
+}
+/**
+ * Inclusive lower bound for a period — the oldest instant a message may carry and still count
+ * as "in" that period. `today` is midnight today; the rest reach further back.
+ */
+export function ResolveDateJumpCutoff(period, now) {
+    switch (period) {
+        case 'today':
+            return startOfDayBefore(now, 0);
+        case 'yesterday':
+            return startOfDayBefore(now, 1);
+        case 'last-week':
+            return startOfDayBefore(now, 7);
+        case 'last-month':
+            return startOfDayBefore(now, 30);
+    }
+}
+/** The timestamp a jump sorts on. Falsy/invalid stamps are skipped rather than treated as epoch. */
+function detailTime(detail) {
+    const raw = detail.__mj_CreatedAt;
+    if (!raw) {
+        return null;
+    }
+    const ms = raw instanceof Date ? raw.getTime() : new Date(raw).getTime();
+    return Number.isNaN(ms) ? null : ms;
+}
+/**
+ * Resolves which loaded message a date jump should land on.
+ *
+ * The target is the OLDEST message at or after the cutoff — jumping to "last week" means the
+ * start of last week's conversation, not its end.
+ *
+ * `NeedsOlder` is the windowing-aware part. If every loaded message is in-period, the true
+ * start of the period may still be below the loaded window, so the caller pages and asks
+ * again. If any loaded message predates the cutoff, the boundary is already inside the loaded
+ * set and no amount of paging would improve the answer.
+ */
+export function ResolveDateJumpTarget(chronologicalDetails, period, now) {
+    const cutoff = ResolveDateJumpCutoff(period, now).getTime();
+    let target = null;
+    let sawOlderThanCutoff = false;
+    for (const detail of chronologicalDetails) {
+        const ms = detailTime(detail);
+        if (ms === null) {
+            continue;
+        }
+        if (ms < cutoff) {
+            sawOlderThanCutoff = true;
+        }
+        else if (target === null) {
+            target = detail;
+        }
+    }
+    // Nothing in-period AND nothing older loaded => the whole window post-dates the cutoff
+    // only if we also found no target; that still means paging could help.
+    return { Detail: target, NeedsOlder: !sawOlderThanCutoff };
+}
+/** Human-readable result, for the caller to surface instead of failing silently. */
+export function DescribeDateJumpOutcome(outcome, period) {
+    const label = period === 'last-week' ? 'last week'
+        : period === 'last-month' ? 'last month'
+            : period;
+    switch (outcome) {
+        case 'reached':
+            return `Jumped to ${label}.`;
+        case 'oldest':
+            return `No messages from ${label} — showing the start of the conversation.`;
+        case 'capped':
+            return `Stopped after loading ${DATE_JUMP_MAX_PAGES} pages — showing the oldest loaded message.`;
+        case 'empty':
+            return 'Nothing loaded to jump to.';
+    }
+}
+/**
+ * Final outcome for a date jump.
+ *
+ * The paging loop and the scroll answer DIFFERENT questions: the loop knows only whether it
+ * ran out of history (or pages) to load, while the scroll knows whether an in-period message
+ * was actually found. Letting the loop's verdict win was a bug — a conversation whose oldest
+ * message is itself in-period never sees a pre-cutoff row, so the loop reports "ran out"
+ * even though the jump landed on a perfectly good target and the user was told no such
+ * messages exist.
+ *
+ * So: a successful scroll always wins. The cap only surfaces when the scroll did NOT reach,
+ * because that is the only case where "we stopped early" explains the miss.
+ */
+export function CombineDateJumpOutcome(scrollOutcome, hitPageCap) {
+    if (scrollOutcome === 'reached') {
+        return 'reached';
+    }
+    return hitPageCap ? 'capped' : scrollOutcome;
+}
+//# sourceMappingURL=date-jump.js.map

package/dist/lib/utils/date-jump.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"date-jump.js","sourceRoot":"","sources":["../../../src/lib/utils/date-jump.ts"],"names":[],"mappings":"AAiBA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,EAAE,CAAC;AAEtC,kDAAkD;AAClD,SAAS,gBAAgB,CAAC,GAAS,EAAE,OAAe;IAChD,MAAM,CAAC,GAAG,IAAI,IAAI,CAAC,GAAG,CAAC,WAAW,EAAE,EAAE,GAAG,CAAC,QAAQ,EAAE,EAAE,GAAG,CAAC,OAAO,EAAE,CAAC,CAAC;IACrE,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,OAAO,EAAE,GAAG,OAAO,CAAC,CAAC;IACjC,OAAO,CAAC,CAAC;AACb,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,qBAAqB,CAAC,MAAsB,EAAE,GAAS;IACnE,QAAQ,MAAM,EAAE,CAAC;QACb,KAAK,OAAO;YACR,OAAO,gBAAgB,CAAC,GAAG,EAAE,CAAC,CAAC,CAAC;QACpC,KAAK,WAAW;YACZ,OAAO,gBAAgB,CAAC,GAAG,EAAE,CAAC,CAAC,CAAC;QACpC,KAAK,WAAW;YACZ,OAAO,gBAAgB,CAAC,GAAG,EAAE,CAAC,CAAC,CAAC;QACpC,KAAK,YAAY;YACb,OAAO,gBAAgB,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC;IACzC,CAAC;AACL,CAAC;AAED,oGAAoG;AACpG,SAAS,UAAU,CAAC,MAAoC;IACpD,MAAM,GAAG,GAAI,MAAoD,CAAC,cAAc,CAAC;IACjF,IAAI,CAAC,GAAG,EAAE,CAAC;QACP,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,MAAM,EAAE,GAAG,GAAG,YAAY,IAAI,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC,IAAI,IAAI,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,CAAC;IACzE,OAAO,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;AACxC,CAAC;AAYD;;;;;;;;;;GAUG;AACH,MAAM,UAAU,qBAAqB,CACjC,oBAAkC,EAClC,MAAsB,EACtB,GAAS;IAET,MAAM,MAAM,GAAG,qBAAqB,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,OAAO,EAAE,CAAC;IAE5D,IAAI,MAAM,GAAa,IAAI,CAAC;IAC5B,IAAI,kBAAkB,GAAG,KAAK,CAAC;IAE/B,KAAK,MAAM,MAAM,IAAI,oBAAoB,EAAE,CAAC;QACxC,MAAM,EAAE,GAAG,UAAU,CAAC,MAAM,CAAC,CAAC;QAC9B,IAAI,EAAE,KAAK,IAAI,EAAE,CAAC;YACd,SAAS;QACb,CAAC;QACD,IAAI,EAAE,GAAG,MAAM,EAAE,CAAC;YACd,kBAAkB,GAAG,IAAI,CAAC;QAC9B,CAAC;aAAM,IAAI,MAAM,KAAK,IAAI,EAAE,CAAC;YACzB,MAAM,GAAG,MAAM,CAAC;QACpB,CAAC;IACL,CAAC;IAED,uFAAuF;IACvF,uEAAuE;IACvE,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU,EAAE,CAAC,kBAAkB,EAAE,CAAC;AAC/D,CAAC;AAED,oFAAoF;AACpF,MAAM,UAAU,uBAAuB,CAAC,OAAwB,EAAE,MAAsB;IACpF,MAAM,KAAK,GAAG,MAAM,KAAK,WAAW,CAAC,CAAC,CAAC,WAAW;QAC9C,CAAC,CAAC,MAAM,KAAK,YAAY,CAAC,CAAC,CAAC,YAAY;YACxC,CAAC,CAAC,MAAM,CAAC;IACb,QAAQ,OAAO,EAAE,CAAC;QACd,KAAK,SAAS;YACV,OAAO,aAAa,KAAK,GAAG,CAAC;QACjC,KAAK,QAAQ;YACT,OAAO,oBAAoB,KAAK,2CAA2C,CAAC;QAChF,KAAK,QAAQ;YACT,OAAO,yBAAyB,mBAAmB,6CAA6C,CAAC;QACrG,KAAK,OAAO;YACR,OAAO,4BAA4B,CAAC;IAC5C,CAAC;AACL,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,sBAAsB,CAClC,aAA8B,EAC9B,UAAmB;IAEnB,IAAI,aAAa,KAAK,SAAS,EAAE,CAAC;QAC9B,OAAO,SAAS,CAAC;IACrB,CAAC;IACD,OAAO,UAAU,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,aAAa,CAAC;AACjD,CAAC","sourcesContent":["import type { RealtimeTimelineSourceDetail } from './realtime-session-timeline';\n\n/**\n * Periods the transcript's date navigator offers. Kept as a union rather than a string so a\n * new dropdown entry cannot silently fall through to \"no cutoff\".\n */\nexport type DateJumpPeriod = 'today' | 'yesterday' | 'last-week' | 'last-month';\n\n/**\n * How far back a jump had to page before it stopped.\n *\n * The plan's requirement is that a jump never silently no-ops, so every terminal state here is\n * something the caller can report: `reached` scrolled to a real message, `oldest` ran out of\n * history, `capped` hit {@link DATE_JUMP_MAX_PAGES}, `empty` had nothing loaded at all.\n */\nexport type DateJumpOutcome = 'reached' | 'oldest' | 'capped' | 'empty';\n\n/**\n * Ceiling on older-page loads for one jump.\n *\n * A jump into a very old conversation would otherwise page the entire history back — the\n * exact unbounded read windowing exists to prevent. On a miss the caller lands the user at\n * the oldest loaded message instead, which is where paging left them anyway.\n */\nexport const DATE_JUMP_MAX_PAGES = 50;\n\n/** Local midnight `daysAgo` days before `now`. */\nfunction startOfDayBefore(now: Date, daysAgo: number): Date {\n    const d = new Date(now.getFullYear(), now.getMonth(), now.getDate());\n    d.setDate(d.getDate() - daysAgo);\n    return d;\n}\n\n/**\n * Inclusive lower bound for a period — the oldest instant a message may carry and still count\n * as \"in\" that period. `today` is midnight today; the rest reach further back.\n */\nexport function ResolveDateJumpCutoff(period: DateJumpPeriod, now: Date): Date {\n    switch (period) {\n        case 'today':\n            return startOfDayBefore(now, 0);\n        case 'yesterday':\n            return startOfDayBefore(now, 1);\n        case 'last-week':\n            return startOfDayBefore(now, 7);\n        case 'last-month':\n            return startOfDayBefore(now, 30);\n    }\n}\n\n/** The timestamp a jump sorts on. Falsy/invalid stamps are skipped rather than treated as epoch. */\nfunction detailTime(detail: RealtimeTimelineSourceDetail): number | null {\n    const raw = (detail as { __mj_CreatedAt?: Date | string | null }).__mj_CreatedAt;\n    if (!raw) {\n        return null;\n    }\n    const ms = raw instanceof Date ? raw.getTime() : new Date(raw).getTime();\n    return Number.isNaN(ms) ? null : ms;\n}\n\nexport interface DateJumpTarget<T extends RealtimeTimelineSourceDetail> {\n    /** Oldest loaded detail at or after the cutoff — the message to scroll to. */\n    Detail: T | null;\n    /**\n     * True when the loaded set cannot yet answer the question: everything loaded is at or\n     * after the cutoff, so an older page might contain a still-earlier message in-period.\n     */\n    NeedsOlder: boolean;\n}\n\n/**\n * Resolves which loaded message a date jump should land on.\n *\n * The target is the OLDEST message at or after the cutoff — jumping to \"last week\" means the\n * start of last week's conversation, not its end.\n *\n * `NeedsOlder` is the windowing-aware part. If every loaded message is in-period, the true\n * start of the period may still be below the loaded window, so the caller pages and asks\n * again. If any loaded message predates the cutoff, the boundary is already inside the loaded\n * set and no amount of paging would improve the answer.\n */\nexport function ResolveDateJumpTarget<T extends RealtimeTimelineSourceDetail>(\n    chronologicalDetails: readonly T[],\n    period: DateJumpPeriod,\n    now: Date\n): DateJumpTarget<T> {\n    const cutoff = ResolveDateJumpCutoff(period, now).getTime();\n\n    let target: T | null = null;\n    let sawOlderThanCutoff = false;\n\n    for (const detail of chronologicalDetails) {\n        const ms = detailTime(detail);\n        if (ms === null) {\n            continue;\n        }\n        if (ms < cutoff) {\n            sawOlderThanCutoff = true;\n        } else if (target === null) {\n            target = detail;\n        }\n    }\n\n    // Nothing in-period AND nothing older loaded => the whole window post-dates the cutoff\n    // only if we also found no target; that still means paging could help.\n    return { Detail: target, NeedsOlder: !sawOlderThanCutoff };\n}\n\n/** Human-readable result, for the caller to surface instead of failing silently. */\nexport function DescribeDateJumpOutcome(outcome: DateJumpOutcome, period: DateJumpPeriod): string {\n    const label = period === 'last-week' ? 'last week'\n        : period === 'last-month' ? 'last month'\n        : period;\n    switch (outcome) {\n        case 'reached':\n            return `Jumped to ${label}.`;\n        case 'oldest':\n            return `No messages from ${label} — showing the start of the conversation.`;\n        case 'capped':\n            return `Stopped after loading ${DATE_JUMP_MAX_PAGES} pages — showing the oldest loaded message.`;\n        case 'empty':\n            return 'Nothing loaded to jump to.';\n    }\n}\n\n/**\n * Final outcome for a date jump.\n *\n * The paging loop and the scroll answer DIFFERENT questions: the loop knows only whether it\n * ran out of history (or pages) to load, while the scroll knows whether an in-period message\n * was actually found. Letting the loop's verdict win was a bug — a conversation whose oldest\n * message is itself in-period never sees a pre-cutoff row, so the loop reports \"ran out\"\n * even though the jump landed on a perfectly good target and the user was told no such\n * messages exist.\n *\n * So: a successful scroll always wins. The cap only surfaces when the scroll did NOT reach,\n * because that is the only case where \"we stopped early\" explains the miss.\n */\nexport function CombineDateJumpOutcome(\n    scrollOutcome: DateJumpOutcome,\n    hitPageCap: boolean\n): DateJumpOutcome {\n    if (scrollOutcome === 'reached') {\n        return 'reached';\n    }\n    return hitPageCap ? 'capped' : scrollOutcome;\n}\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memberjunction/ng-conversations",
-  "version": "6.1.0-edge.2",
+  "version": "6.1.0-edge.4",
   "description": "MemberJunction: Conversation, Collection, and Artifact management components for any Angular application",
   "main": "./dist/public-api.js",
   "typings": "./dist/public-api.d.ts",
@@ -9,13 +9,13 @@
   ],
   "keywords": [],
   "author": "",
-  "license": "ISC",
+  "license": "BUSL-1.1",
   "devDependencies": {
     "@angular/compiler": "21.1.3",
     "@angular/compiler-cli": "21.1.3",
     "sass": "^1.97.3",
     "vitest": "^4.0.18",
-    "@memberjunction/ng-test-utils": "6.1.0-edge.2"
+    "@memberjunction/ng-test-utils": "6.1.0-edge.4"
   },
   "peerDependencies": {
     "@angular/common": "^21.1.3",
@@ -26,35 +26,35 @@
   "dependencies": {
     "@angular/animations": "21.1.3",
     "@angular/cdk": "21.1.3",
-    "@memberjunction/ai": "6.1.0-edge.2",
-    "@memberjunction/ai-agent-client": "6.1.0-edge.2",
-    "@memberjunction/ai-core-plus": "6.1.0-edge.2",
-    "@memberjunction/ai-engine-base": "6.1.0-edge.2",
-    "@memberjunction/ai-realtime-client": "6.1.0-edge.2",
-    "@memberjunction/conversations-runtime": "6.1.0-edge.2",
-    "@memberjunction/core": "6.1.0-edge.2",
-    "@memberjunction/core-entities": "6.1.0-edge.2",
-    "@memberjunction/global": "6.1.0-edge.2",
-    "@memberjunction/graphql-dataprovider": "6.1.0-edge.2",
-    "@memberjunction/interactive-component-types": "6.1.0-edge.2",
-    "@memberjunction/ng-agent-client": "6.1.0-edge.2",
-    "@memberjunction/ng-artifacts": "6.1.0-edge.2",
-    "@memberjunction/ng-base-types": "6.1.0-edge.2",
-    "@memberjunction/ng-code-editor": "6.1.0-edge.2",
-    "@memberjunction/ng-composer": "6.1.0-edge.2",
-    "@memberjunction/ng-container-directives": "6.1.0-edge.2",
-    "@memberjunction/ng-forms": "6.1.0-edge.2",
-    "@memberjunction/ng-markdown": "6.1.0-edge.2",
-    "@memberjunction/ng-media-player": "6.1.0-edge.2",
-    "@memberjunction/ng-notifications": "6.1.0-edge.2",
-    "@memberjunction/ng-resource-permissions": "6.1.0-edge.2",
-    "@memberjunction/ng-shared-generic": "6.1.0-edge.2",
-    "@memberjunction/ng-task-graph-editor": "6.1.0-edge.2",
-    "@memberjunction/ng-tasks": "6.1.0-edge.2",
-    "@memberjunction/ng-testing": "6.1.0-edge.2",
-    "@memberjunction/ng-ui-components": "6.1.0-edge.2",
-    "@memberjunction/ng-user-routines": "6.1.0-edge.2",
-    "@memberjunction/ng-whiteboard": "6.1.0-edge.2",
+    "@memberjunction/ai": "6.1.0-edge.4",
+    "@memberjunction/ai-agent-client": "6.1.0-edge.4",
+    "@memberjunction/ai-core-plus": "6.1.0-edge.4",
+    "@memberjunction/ai-engine-base": "6.1.0-edge.4",
+    "@memberjunction/ai-realtime-client": "6.1.0-edge.4",
+    "@memberjunction/conversations-runtime": "6.1.0-edge.4",
+    "@memberjunction/core": "6.1.0-edge.4",
+    "@memberjunction/core-entities": "6.1.0-edge.4",
+    "@memberjunction/global": "6.1.0-edge.4",
+    "@memberjunction/graphql-dataprovider": "6.1.0-edge.4",
+    "@memberjunction/interactive-component-types": "6.1.0-edge.4",
+    "@memberjunction/ng-agent-client": "6.1.0-edge.4",
+    "@memberjunction/ng-artifacts": "6.1.0-edge.4",
+    "@memberjunction/ng-base-types": "6.1.0-edge.4",
+    "@memberjunction/ng-code-editor": "6.1.0-edge.4",
+    "@memberjunction/ng-composer": "6.1.0-edge.4",
+    "@memberjunction/ng-container-directives": "6.1.0-edge.4",
+    "@memberjunction/ng-forms": "6.1.0-edge.4",
+    "@memberjunction/ng-markdown": "6.1.0-edge.4",
+    "@memberjunction/ng-media-player": "6.1.0-edge.4",
+    "@memberjunction/ng-notifications": "6.1.0-edge.4",
+    "@memberjunction/ng-resource-permissions": "6.1.0-edge.4",
+    "@memberjunction/ng-shared-generic": "6.1.0-edge.4",
+    "@memberjunction/ng-task-graph-editor": "6.1.0-edge.4",
+    "@memberjunction/ng-tasks": "6.1.0-edge.4",
+    "@memberjunction/ng-testing": "6.1.0-edge.4",
+    "@memberjunction/ng-ui-components": "6.1.0-edge.4",
+    "@memberjunction/ng-user-routines": "6.1.0-edge.4",
+    "@memberjunction/ng-whiteboard": "6.1.0-edge.4",
     "angular-split": "^20.0.0",
     "rxjs": "^7.8.2",
     "tslib": "^2.8.1"