@fileverse-dev/dsheet 4.1.23-stabilise-package-3 → 4.1.23-stabilise-package-5

package/dist/editor/contexts/editor-context.d.ts

@@ -37,6 +37,8 @@ export interface EditorContextType {
     rebuildLocalStore: () => Promise<void>;
     sheetEditorRef: React.MutableRefObject<WorkbookInstance | null>;
     setSheetEditorRef: React.RefCallback<WorkbookInstance>;
+    /** Call when the active sheet changes or sheets appear; lets the keeper remember or restore it. */
+    notifyActiveSheetChange: () => void;
     ydocRef: React.MutableRefObject<Y.Doc | null>;
     persistenceRef: React.MutableRefObject<IndexeddbPersistence | null>;
     sheetData: Sheet[];

package/dist/editor/hooks/use-celldata-compaction.d.ts

@@ -1,7 +1,8 @@
 import { MutableRefObject, RefObject } from 'react';
 import { WorkbookInstance, Sheet } from '../../sheet-engine/react';
+import { planYdocCompaction } from '../utils/compact-committed-celldata';
 
-import type * as Y from 'yjs';
+import * as Y from 'yjs';
 type UseCelldataCompactionArgs = {
     dsheetId: string;
     ydocRef: RefObject<Y.Doc | null>;
@@ -12,11 +13,31 @@ type UseCelldataCompactionArgs = {
     isDataLoaded: boolean;
     isReadOnly: boolean;
     remoteUpdateRef: MutableRefObject<boolean>;
+    /** True while a structural remote change waits to remount the Workbook. */
+    structuralRemountPendingRef?: MutableRefObject<boolean>;
     collabSyncing: boolean;
 };
+/**
+ * False while a remote apply is running, while a structural remount is pending
+ * (the engine still has the old grid and the Yjs document has the new one) or
+ * while collaboration is still syncing.
+ */
+export declare function canRunCompaction(refs: {
+    remoteUpdateRef: MutableRefObject<boolean>;
+    structuralRemountPendingRef?: MutableRefObject<boolean>;
+}, collabSyncing: boolean): boolean;
+/**
+ * Applies the plan chunk by chunk, yielding between chunks. The plan was made
+ * from the document as it was, and one change in it, the whole-value
+ * borderInfo write, would overwrite a newer value. So the run stops, leaving
+ * the compaction unfinished (it is retried on a later open), as soon as the
+ * document differs from what the previous chunk left. Returns true when every
+ * chunk was applied.
+ */
+export declare function applyCompactionChangesInChunks(ydoc: Y.Doc, dsheetId: string, changes: ReturnType<typeof planYdocCompaction>['changes'], handleOnChangePortalUpdate: () => void, isCancelled: () => boolean, sheetEditorRef: RefObject<WorkbookInstance | null>, chunkSize?: number): Promise<boolean>;
 /**
  * One-shot background compaction (celldata + borderInfo). Completion is stored
  * on the anchor sheet's config in Yjs so it syncs across devices.
  */
-export declare function useCelldataCompaction({ dsheetId, ydocRef, sheetEditorRef, currentDataRef, handleOnChangePortalUpdate, syncStatus, isDataLoaded, isReadOnly, remoteUpdateRef, collabSyncing, }: UseCelldataCompactionArgs): void;
+export declare function useCelldataCompaction({ dsheetId, ydocRef, sheetEditorRef, currentDataRef, handleOnChangePortalUpdate, syncStatus, isDataLoaded, isReadOnly, remoteUpdateRef, structuralRemountPendingRef, collabSyncing, }: UseCelldataCompactionArgs): void;
 export {};

package/dist/editor/hooks/use-celldata-compaction.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/editor/utils/active-sheet-keeper.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/editor/utils/remote-apply-guard.d.ts

@@ -34,26 +34,23 @@ export type StructuralRemountRefs = RemoteApplyGuardRefs & {
 /**
  * Debounced structural remount under the remote-apply guard.
  *
- * The guard is begun once, right before `run`, and ended after paint, so each
- * remount owns exactly one begin and one end. It is NOT held while the timer
- * is merely pending or deferred by a cell edit: `remoteUpdateRef` makes
- * handleChange and the data-block work in afterUpdateCell drop local work, so
- * holding it across an edit would drop the user's typed edit. (The cell write
- * in afterUpdateCell and the commit-time write do not check it.) What must not
- * run while a remount is pending is the engine → Yjs echo hooks, which diff
- * the old grid against Yjs: they check `shouldSkipEchoWrite`. Events that
- * land while one is pending only re-arm its timer.
+ * Each pending remount owns exactly one begin and one end (B1): the guard is
+ * begun when the remount becomes pending (no remount was pending before),
+ * held while the timer is pending or deferred by a cell edit (B3), and ended
+ * after paint once `run` has finished. Events that land while one is pending
+ * only re-arm its timer.
  *
  * While `isEditing()` is true at fire time the timer re-arms (250 ms) and the
- * pending flag is kept; the remount runs once the edit ends.
+ * pending flag and guard depth are kept; the remount runs once the edit ends.
+ * The typed cell itself is still written: the commit-time write and the cell
+ * write in afterUpdateCell do not check the guard.
  */
 export declare function scheduleStructuralRemount(refs: StructuralRemountRefs, run: () => void, delayMs?: number, isEditing?: () => boolean): void;
 /** Re-arm interval while a cell edit blocks the remount. */
 export declare const STRUCTURAL_REMOUNT_EDIT_RETRY_MS = 250;
 /**
- * Drop a pending structural remount (observer teardown). The guard is only
- * held while `run` executes and until paint afterwards, so there is nothing
- * to release here.
+ * Drop a pending structural remount (observer teardown) and release the
+ * guard begun for it.
  */
 export declare function cancelStructuralRemount(refs: StructuralRemountRefs): void;
 /**

package/dist/editor/utils/structural-edit-other-tabs.test.d.ts

@@ -0,0 +1 @@
+export {};