@jielga/tmdatagrid 2.0.0-beta.19 → 2.0.0-beta.20

package/dist/index.d.ts

@@ -307,6 +307,14 @@ type TMDataGridEditState = {
   }>;
   /** The draft store's delete slice: rows marked deleted, awaiting the save. */
   deletedRowIds: ReadonlyArray<string>;
+  /**
+   * `true` while `saveDrafts` is in flight - from the call until the
+   * consumer's callbacks (`onSaveDrafts`, or the per-row `onCommit` /
+   * `onRowAdd` / `onRowDelete` loop) have settled. Concurrent `saveDrafts`
+   * calls join the same run, so it flips once per run. It stays `false` for
+   * a save that finds nothing to send.
+   */
+  isSaving: boolean;
 };
 type ErasedRow$1 = Row<TMDataGridFeatures, TMDataGridRowData>;
 type ErasedColumn$1 = Column<TMDataGridFeatures, TMDataGridRowData, unknown>;
@@ -2421,9 +2429,10 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
   enablePagination?: boolean;
   /**
    * Sends the grid back to the first page whenever the query changes - a
-   * column filter, the quick search or the sort. Defaults to `true` under
-   * `manualPagination` and `false` otherwise, where TanStack's own
-   * `autoResetPageIndex` already does it.
+   * column filter, the quick search, the sort or the grouping. On by
+   * default. TanStack's own `autoResetPageIndex` is switched off by the
+   * grid: it fires on any change to the `data` array, which under
+   * `editing.draft` is every commit.
    *
    * Server-side, `pageIndex` is a position in a result set the grid does not
    * own: narrowing the query leaves it pointing past the last page, and the
@@ -2976,8 +2985,10 @@ type TMDataGridDraftActionsState = {
    * Reads as `draftCount + openCount`; use whichever you meant.
    */
   pendingCount: number;
-  /** Whether a submit is in flight. */
+  /** Whether a submit is in flight - any open row is submitting. */
   isSubmitting: boolean;
+  /** `true` while `saveDrafts` is in flight. */
+  isSaving: boolean;
 };
 /** What the edit chrome can do. */
 type TMDataGridDraftActionsActions = {