@abraca/dabra 2.17.1 → 2.18.0

package/dist/index.d.ts

@@ -3281,6 +3281,24 @@ declare class BackgroundSyncManager extends EventEmitter {
    */
   init(): Promise<void>;
   private _loadPersistedStates;
+  /**
+   * Re-read persisted sync states from IndexedDB, merging in any docs not
+   * already tracked in memory. Unlike `init()` this is **not** cached behind
+   * `_initPromise` — every call hits IDB afresh.
+   *
+   * Why this exists: `init()` only ever loads IDB once. If a manager was
+   * created while IDB was empty/mid-population (or a UI singleton was left
+   * pointing at a manager whose in-memory map is stale after a connection
+   * swap), the only thing that recovered the real counts was a full page
+   * reload (which spins up a brand-new manager → fresh `_loadPersistedStates`).
+   * Calling this re-hydrates from the same source a reload reads, so the
+   * offline-sync panel can self-heal from a spurious "0/0" without a reload.
+   *
+   * Merge-only by design: an in-memory entry (possibly a fresher in-flight
+   * `syncing`/`synced`) is never clobbered by the persisted copy; we only add
+   * docs IDB knows about that memory doesn't.
+   */
+  reloadPersistedStates(): Promise<void>;
   /** Sync all documents in the root tree. */
   syncAll(): Promise<void>;
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abraca/dabra",
-  "version": "2.17.1",
+  "version": "2.18.0",
   "description": "abracadabra provider",
   "keywords": [
     "abracadabra",
@@ -41,7 +41,7 @@
     "yjs": "^13.6.8"
   },
   "devDependencies": {
-    "@abraca/schema": "2.17.1"
+    "@abraca/schema": "2.18.0"
   },
   "scripts": {
     "test": "node --no-warnings --conditions=source --experimental-transform-types --test 'tests/*.test.ts'"

package/src/BackgroundSyncManager.ts

@@ -199,6 +199,36 @@ export class BackgroundSyncManager extends EventEmitter {
 		}
 	}
 
+	/**
+	 * Re-read persisted sync states from IndexedDB, merging in any docs not
+	 * already tracked in memory. Unlike `init()` this is **not** cached behind
+	 * `_initPromise` — every call hits IDB afresh.
+	 *
+	 * Why this exists: `init()` only ever loads IDB once. If a manager was
+	 * created while IDB was empty/mid-population (or a UI singleton was left
+	 * pointing at a manager whose in-memory map is stale after a connection
+	 * swap), the only thing that recovered the real counts was a full page
+	 * reload (which spins up a brand-new manager → fresh `_loadPersistedStates`).
+	 * Calling this re-hydrates from the same source a reload reads, so the
+	 * offline-sync panel can self-heal from a spurious "0/0" without a reload.
+	 *
+	 * Merge-only by design: an in-memory entry (possibly a fresher in-flight
+	 * `syncing`/`synced`) is never clobbered by the persisted copy; we only add
+	 * docs IDB knows about that memory doesn't.
+	 */
+	async reloadPersistedStates(): Promise<void> {
+		try {
+			const states = await this.persistence.getAllStates();
+			for (const state of states) {
+				if (!this.syncStates.has(state.docId)) {
+					this.syncStates.set(state.docId, state);
+				}
+			}
+		} catch {
+			// IDB unavailable — keep whatever is already in memory.
+		}
+	}
+
 	/** Sync all documents in the root tree. */
 	async syncAll(): Promise<void> {
 		if (this._destroyed) return;