@jielga/tmdatagrid 2.0.0-beta.15 → 2.0.0-beta.17

package/dist/index.d.ts

@@ -642,15 +642,17 @@ type TMDataGridEditApi<TData extends RowData = TMDataGridRowData> = {
    */
   addRow: (values?: Partial<TData>) => string;
   /**
-   * Opens entry rows for a list of records at once - one state write for the
+   * Opens entry rows for a list of records at once - one publish for the
    * batch, where a loop over `addRow` is one per row. Each row is seeded over
    * `newRowDefaults` exactly as `addRow` does.
    *
-   * `commit: true` submits each row as it lands, which is what an import
-   * wants: rows that validate commit (parked in the draft store under
-   * `editing.draft`, added through `onRowAdd` without it - once per row),
-   * and rows that fail stay open in the entry block carrying their errors,
-   * for the user to fix. The result says which went which way.
+   * `commit: true` submits the rows too, which is what an import wants: rows
+   * that validate commit, and rows that fail stay open in the entry block
+   * carrying their errors, for the user to fix. The result says which went
+   * which way. Under `editing.draft` the rows validate together and land in
+   * the draft store in the same publish as the add - the grid renders once,
+   * whatever the count. Without it each valid row goes out through
+   * `onRowAdd`, one at a time and in order.
    */
   addRows: (rows: ReadonlyArray<Partial<TData>>, options?: TMDataGridAddRowsOptions) => Promise<TMDataGridAddRowsResult>;
   /**