ngx-dynamic-entity 1.4.0 → 1.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-dynamic-entity",
-  "version": "1.4.0",
+  "version": "1.6.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.4.0",
+    "@dynamic-entity/core": "^1.6.0",
     "rxjs": "^7.0.0"
   },
   "keywords": [

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

@@ -798,8 +798,20 @@ declare class DynamicFormComponent implements OnInit, OnChanges, OnDestroy {
     ngOnInit(): void;
     ngOnChanges(changes: SimpleChanges): void;
     ngOnDestroy(): void;
-    setActiveTab(tabId: string): void;
-    setActiveSubTab(subTabId: string): void;
+    /**
+     * `focusPanel: false` is for a caller that is about to focus something more specific.
+     *
+     * Activating a tab moves focus into its panel, which is right for a keyboard user pressing
+     * a tab. A quick-jump also switches tabs, but then focuses the field it was aiming at — and
+     * the panel focus runs on `requestAnimationFrame`, after `afterNextRender`, so it landed
+     * second and took the focus back every time. Saying so is better than out-timing it.
+     */
+    setActiveTab(tabId: string, options?: {
+        focusPanel?: boolean;
+    }): void;
+    setActiveSubTab(subTabId: string, options?: {
+        focusPanel?: boolean;
+    }): void;
     getFieldSpan(field: NestedFieldConfig): string;
     /** A critical field stays read-only until the user deliberately unlocks it. */
     isFieldLocked(field: NestedFieldConfig): boolean;
@@ -866,9 +878,8 @@ declare class DynamicFormComponent implements OnInit, OnChanges, OnDestroy {
      * `flattenFormValues` keys by bare id, so one of the two silently wins and the rule reads
      * whichever landed there.
      *
-     * `validateConfig` catches this for `showWhen` and cascade parents, which live in the
-     * config. Rules do not: they arrive as a separate `@Input`, so the config alone cannot be
-     * checked for them and this is the only place both are in hand.
+     * `validateConfig({ rules })` catches this statically. The check here remains because
+     * consumers that never call the validator still get a signal in development.
      */
     private warnAmbiguousRuleReferences;
     private static readonly warnedAmbiguousIds;
@@ -1000,6 +1011,7 @@ declare class DynamicRecordFormComponent implements OnChanges {
     }>;
     dynamicFormComp?: DynamicFormComponent;
     private readonly rulesEvaluation;
+    private readonly rbacService;
     private readonly host;
     private readonly injector;
     readonly currentData: i0.WritableSignal<Record<string, any>>;
@@ -1024,6 +1036,16 @@ declare class DynamicRecordFormComponent implements OnChanges {
         message: string;
     }[];
     dismissInfoBanner(fieldId: string): void;
+    /**
+     * Whether the current roles may edit this record.
+     *
+     * `userRoles` was declared as an input here and then read by nothing at all — this
+     * component computed no permissions of any kind, so the record view was fully editable
+     * for every role while the plain form at least hid its Save button. Cached on the same
+     * terms as the sibling component: it depends only on `config` and `userRoles`.
+     */
+    private permissionsCache;
+    get permissions(): ReturnType<RbacService['getPermissions']>;
     /** True when nothing in the record may be edited. */
     get recordReadOnly(): boolean;
     /**