uapp-communication-sdk 1.0.0-dev.95 → 1.0.0-dev.97

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uapp-communication-sdk",
-  "version": "1.0.0-dev.95",
+  "version": "1.0.0-dev.97",
   "description": "Embeddable Communication Hub widgets (chat, feed, bookings, schedule).",
   "type": "module",
   "types": "./types/sdk/index.d.ts",

package/types/features/calls/presentation/CallCenter.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"CallCenter.d.ts","sourceRoot":"","sources":["../../../../../../src/features/calls/presentation/CallCenter.tsx"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAqB,MAAM,OAAO,CAAC;AAU7D;;;;GAIG;AACH,eAAO,MAAM,UAAU,QAAO,YAAY,GAAG,IAyF5C,CAAC"}
+{"version":3,"file":"CallCenter.d.ts","sourceRoot":"","sources":["../../../../../../src/features/calls/presentation/CallCenter.tsx"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,YAAY,EAAqB,MAAM,OAAO,CAAC;AAU7D;;;;GAIG;AACH,eAAO,MAAM,UAAU,QAAO,YAAY,GAAG,IA0F5C,CAAC"}

package/types/features/calls/presentation/use-call-heartbeat.d.ts

@@ -1,26 +1,38 @@
+import type { CallPhase } from '../store/call-store';
 /**
- * How often a client in a connected call reports that it is still there. Matches the backend's
+ * How often a client in a CONNECTED call reports that it is still there. Matches the backend's
  * `CallConsts.HeartbeatIntervalSeconds` — the server's freshness and reclaim windows are sized as
  * multiples of this, so the two must not drift apart.
  */
 export declare const CALL_HEARTBEAT_INTERVAL_MS = 15000;
 /**
- * Keeps the server informed that this client is still in the call, and listens to what it says back.
+ * The far faster cadence while a call is merely RINGING (`CallConsts.RingingHeartbeatIntervalSeconds`).
  *
- * <p><b>Why it exists.</b> A call leaves Active only when a client asks it to, and the case that broke
- * was the one where neither client can ask: both networks drop, so both people went on reading as "in a
- * call" indefinitely with nothing anywhere to correct it. The server cannot observe the difference —
- * a dropped connection looks exactly like a closed laptop, and the media runs through the provider where
- * it cannot look at all. A beat is the only positive evidence it ever gets.</p>
+ * <p>Ringing is short and rare, so the extra traffic is trivial; what it buys is the only thing that
+ * makes a caller's disappearance detectable in seconds rather than in most of a minute — the case where
+ * somebody closes the tab straight after dialling and the other person's phone rings on for a call with
+ * nobody behind it. During a conversation the opposite trade applies: it runs for minutes or hours, and
+ * beating fast would buy nothing.</p>
+ */
+export declare const CALL_RINGING_HEARTBEAT_INTERVAL_MS = 3000;
+/**
+ * Keeps the server informed that this client is still on this call, and listens to what it says back.
+ *
+ * <p><b>Why it exists.</b> A call leaves its live states only when a client asks it to, and the cases
+ * that broke were the ones where no client can ask: both networks drop mid-call and both people go on
+ * reading as "in a call" indefinitely; or a caller closes the tab and the callee's phone rings on for a
+ * call nobody is behind. The server cannot observe the difference — a dropped connection looks exactly
+ * like a closed laptop, and the media runs through the provider where it cannot look at all. A beat is
+ * the only positive evidence it ever gets.</p>
  *
  * <p><b>And the other direction.</b> The reply says whether the call still exists. A call can end while
  * this client is unreachable — the other party hung up during a blip, or the server reclaimed it — and
- * the push announcing that reached nobody, with nothing to repeat it. Without reading the reply, a client
- * returning from a blip would hold a dead call on screen until the person closed it themselves.</p>
+ * the push announcing that reached nobody, with nothing to repeat it. Without reading the reply, a
+ * client returning from a blip would hold a dead call on screen until the person closed it themselves.</p>
  *
  * <p>A failed beat is deliberately NOT treated as evidence of anything. The network wobbling is exactly
- * when beats fail, and tearing the call down on one lost request would end calls that are perfectly fine.
- * Only an explicit "this call is over" from the server ends anything here.</p>
+ * when beats fail, and tearing the call down on one lost request would end calls that are perfectly
+ * fine. Only an explicit "this call is over" from the server ends anything here.</p>
  */
-export declare const useCallHeartbeat: (callId: string | null, isActive: boolean) => void;
+export declare const useCallHeartbeat: (callId: string | null, phase: CallPhase) => void;
 //# sourceMappingURL=use-call-heartbeat.d.ts.map

package/types/features/calls/presentation/use-call-heartbeat.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"use-call-heartbeat.d.ts","sourceRoot":"","sources":["../../../../../../src/features/calls/presentation/use-call-heartbeat.ts"],"names":[],"mappings":"AAGA;;;;GAIG;AACH,eAAO,MAAM,0BAA0B,QAAS,CAAC;AAEjD;;;;;;;;;;;;;;;;;GAiBG;AACH,eAAO,MAAM,gBAAgB,GAAI,QAAQ,MAAM,GAAG,IAAI,EAAE,UAAU,OAAO,KAAG,IA2C3E,CAAC"}
+{"version":3,"file":"use-call-heartbeat.d.ts","sourceRoot":"","sources":["../../../../../../src/features/calls/presentation/use-call-heartbeat.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAGrD;;;;GAIG;AACH,eAAO,MAAM,0BAA0B,QAAS,CAAC;AAEjD;;;;;;;;GAQG;AACH,eAAO,MAAM,kCAAkC,OAAQ,CAAC;AAgBxD;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,gBAAgB,GAAI,QAAQ,MAAM,GAAG,IAAI,EAAE,OAAO,SAAS,KAAG,IA4C1E,CAAC"}