@rivium/push-web 0.1.8 → 0.1.10

package/dist/index.d.ts

@@ -466,6 +466,20 @@ declare class RiviumPush {
      * Unsubscribe from a topic
      */
     unsubscribeTopic(topic: string): Promise<void>;
+    /**
+     * Show an OS notification for a message the app received while its page was
+     * visible.
+     *
+     * A message that arrives over the real-time connection is handed to
+     * `onMessage` and, while the page is visible, deliberately not shown as an
+     * OS notification - the app is in front and usually shows its own UI. Some
+     * messages still deserve one: a chat message for a conversation the user is
+     * not reading, for instance. The app knows that; the SDK does not.
+     *
+     * Goes through the service worker when there is one, so clicks are handled
+     * the same way as a notification the worker showed itself.
+     */
+    showNotification(message: RiviumPushMessage): void;
     /**
      * Check if connected to MQTT broker
      */
@@ -649,6 +663,19 @@ declare class RiviumPush {
     private showRichNotification;
     private updateFaviconBadge;
     private setConnectionState;
+    /**
+     * The id the BACKEND uses in MQTT topics: the first 16 characters of the
+     * project id, returned as `appId` by /devices/register.
+     *
+     * Channels were built from the API key prefix instead, so every channel this
+     * SDK streamed from was one nothing is ever published to - the real-time
+     * path silently delivered nothing on web, from 0.1.0 until 0.1.9. It went
+     * unnoticed because Web Push carried every message on its own.
+     *
+     * The API key prefix stays as the fallback for a backend old enough not to
+     * return `appId`; the native SDKs do exactly the same.
+     */
+    private topicAppId;
     private getOrCreateDeviceId;
     private generateUUID;
     private urlBase64ToUint8Array;