ngx-dynamic-entity-builder 1.7.0 → 1.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-dynamic-entity-builder",
-  "version": "1.7.0",
+  "version": "1.8.0",
   "description": "Angular standalone visual builder for authoring dynamic-entity EntityConfig (fields, tabs, validators, RBAC).",
   "//typings": "Local workspace resolution only: ng-packagr 21 writes types/ngx-dynamic-entity-builder.d.ts into dist/package.json. Do NOT add a 'main' field here — ng-packagr does not generate one, so it would be copied verbatim and resolve wrongly in the published package.",
   "typings": "types/ngx-dynamic-entity-builder.d.ts",
@@ -10,8 +10,8 @@
     "@angular/core": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
     "@angular/forms": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
     "@angular/material": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
-    "@dynamic-entity/core": "^1.7.0",
-    "ngx-dynamic-entity": "^1.7.0",
+    "@dynamic-entity/core": "^1.8.0",
+    "ngx-dynamic-entity": "^1.8.0",
     "rxjs": "^7.0.0"
   },
   "keywords": [

package/types/ngx-dynamic-entity-builder.d.ts

@@ -46,6 +46,39 @@ declare class BuilderStore {
      * made any role-checking predicate answer false for everyone.
      */
     private readonly _userRoles;
+    private readonly history;
+    private readonly cursor;
+    private readonly historyLength;
+    private lastEditAt;
+    /** Consecutive edits closer together than this fold into one undo step. */
+    private static readonly COALESCE_MS;
+    readonly canUndo: _angular_core.Signal<boolean>;
+    readonly canRedo: _angular_core.Signal<boolean>;
+    /**
+     * Fold the current state into history.
+     *
+     * Called explicitly by the write paths rather than from an `effect`. An effect would have
+     * been fewer call sites, but it requires an injection context: `BuilderStore` had no
+     * constructor, so `new BuilderStore()` was legal, and adding one broke every caller that
+     * did it with NG0203. Explicit calls also make the timing deterministic — a test can
+     * assert straight after an edit instead of flushing effects first.
+     *
+     * Calling it twice for one operation is harmless: the second call sees the same signal
+     * references already at the cursor and returns.
+     *
+     * `setFieldLabel` is bound to a keystroke, so recording every emission would make undo
+     * walk back one character at a time. Two consecutive edits merge when they land inside
+     * `COALESCE_MS` *and* the structure is unchanged — a rename coalesces, while adding,
+     * removing or moving anything always earns its own step however fast it is clicked.
+     */
+    private record;
+    /** Counts that distinguish a structural edit from a value edit. */
+    private shapeOf;
+    /** Start history again from the state just loaded. Nothing before it is undoable. */
+    private resetHistory;
+    undo(): void;
+    redo(): void;
+    private applyHistory;
     readonly config: _angular_core.Signal<EntityFormConfig>;
     readonly selectedFieldId: _angular_core.Signal<string>;
     readonly activeLanguage: _angular_core.Signal<string>;
@@ -359,6 +392,13 @@ declare class EntityBuilderComponent implements OnChanges {
     save: EventEmitter<EntityFormConfig>;
     protected readonly rbacActions: (keyof EntityPermissions)[];
     constructor();
+    /**
+     * Ctrl/Cmd+Z and Ctrl/Cmd+Shift+Z, but only when the user is not typing.
+     *
+     * A textarea or input has its own undo stack, and hijacking it would make Ctrl+Z revert a
+     * whole structural edit when the author only wanted to take back a character.
+     */
+    protected onKeydown(event: KeyboardEvent): void;
     ngOnChanges(changes: SimpleChanges): void;
     protected doSave(): void;
     protected get json(): string;