@one-grid-core/angular 0.5.0 → 0.5.1

package/lib/core/instants/one-grid-api.class.d.ts

@@ -1,6 +1,6 @@
 import { OneColumnDef, OneColumnStateEntry } from '../models/one-column-def-types.model';
 import { OneRowNode } from "./one-row-node.class";
-import { OneGridInitOptions, OneGridType, OneSortModel } from '../models/one-grid-types.model';
+import { OneGridInitOptions, OneGridType, OneRowTransaction, OneSortModel } from '../models/one-grid-types.model';
 import { OneGridEventService } from '../services/one-grid-event.service';
 import { OneGridSelectionService } from '../services/one-grid-selection.service';
 import { OneRowValidationErrors, OneValidationResult } from '../models/one-validation.model';
@@ -89,6 +89,18 @@ export declare class OneGridApi<T = any> {
      * and there is nothing left to match against.
      */
     updateRowData(rowData: T[]): void;
+    /**
+     * Apply a batch of row changes without the host rebinding the dataset:
+     * append rows (at the root, or under a parent by id on tree data), replace
+     * rows by id, drop rows at any depth. Selection and expansion survive —
+     * this is `updateRowData` fed from the grid's own current rows, so the
+     * host keeps no parallel copy to reconcile.
+     *
+     * Requires a stable `context.componentParent.getRowId`: rows are matched by
+     * id, and without an id function there is nothing to match on — the
+     * transaction is refused with a warning rather than half-applied.
+     */
+    applyTransaction(transaction: OneRowTransaction<T>): void;
     /**
      * The one row-loading path. `setRowData` and `updateRowData` differed only in
      * whether they cleared the state services first, so everything else — build,

package/lib/core/models/one-grid-types.model.d.ts

@@ -58,6 +58,25 @@ export interface OneSortModel<T = any> {
     colId: keyof T;
     sort: 'asc' | 'desc';
 }
+/**
+ * One batch of row changes for `api.applyTransaction` — the way to append,
+ * patch or drop rows without rebinding the whole dataset from the host.
+ *
+ * Rows are matched by id, so a transaction requires a
+ * `context.componentParent.getRowId`. Selection and expansion survive, the
+ * active sort and filters re-apply, and on tree data `remove` reaches any
+ * depth while `addToParentId` places added rows under an existing parent.
+ */
+export interface OneRowTransaction<T = any> {
+    /** Rows to append — at the root, or under `addToParentId`. */
+    add?: T[];
+    /** Row id of the parent the added rows go under (tree data only). */
+    addToParentId?: string;
+    /** Replacement rows, matched to existing rows by id. */
+    update?: T[];
+    /** Rows (or row ids) to drop, at any depth. */
+    remove?: (T | string)[];
+}
 export interface GridRowData {
     rowId: string;
     [key: string]: any;

package/lib/core/services/one-grid-row.service.d.ts

@@ -10,6 +10,13 @@ export declare class OneGridRowService {
      * Generate Unique Row ID
      */
     generateRowId(data: any, rowIndex: number): string;
+    /**
+     * The row's id, or null when it cannot be known — no id function, or one
+     * that answers nothing for this row. Unlike `generateRowId` this never
+     * mints an id, which is what row matching (transactions) needs: a minted
+     * id matches nothing and must not pretend otherwise.
+     */
+    resolveRowId(data: any): string | null;
     static ɵfac: i0.ɵɵFactoryDeclaration<OneGridRowService, never>;
     static ɵprov: i0.ɵɵInjectableDeclaration<OneGridRowService>;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@one-grid-core/angular",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "OneGrid — a feature-rich Angular data grid component with tree data, master/detail, editing, selection, pagination, and virtual scrolling.",
   "keywords": [
     "angular",