ngx-dynamic-entity 1.7.0 → 1.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-dynamic-entity",
-  "version": "1.7.0",
+  "version": "1.8.0",
   "description": "Angular standalone UI library for rendering dynamic entity forms.",
   "//typings": "Local workspace resolution only: ng-packagr 21 writes types/ngx-dynamic-entity.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.d.ts",
@@ -8,7 +8,7 @@
     "@angular/common": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
     "@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",
-    "@dynamic-entity/core": "^1.7.0",
+    "@dynamic-entity/core": "^1.8.0",
     "rxjs": "^7.0.0"
   },
   "keywords": [

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

@@ -816,6 +816,15 @@ declare class DynamicFormComponent implements OnInit, OnChanges, OnDestroy {
     get submitBlocked(): boolean;
     ngOnInit(): void;
     ngOnChanges(changes: SimpleChanges): void;
+    /**
+     * Whether an `initialData` change represents loading a different record.
+     *
+     * Not every change does. A template binding like `[initialData]="record() || {}"` yields a
+     * fresh object literal on each evaluation, so `ngOnChanges` fires with two empty objects
+     * and nothing has actually been loaded — resetting there would drag someone back to the
+     * first tab while they were filling in a new record on the third.
+     */
+    private isRecordSwap;
     ngOnDestroy(): void;
     /**
      * `focusPanel: false` is for a caller that is about to focus something more specific.