ngx-dynamic-entity 1.9.0 → 1.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-dynamic-entity",
-  "version": "1.9.0",
+  "version": "1.10.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.9.0",
+    "@dynamic-entity/core": "^1.10.0",
     "rxjs": "^7.0.0"
   },
   "keywords": [

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

@@ -1252,9 +1252,22 @@ declare class DynamicRecordFormComponent implements OnChanges {
         tabId: string;
         record: Record<string, any>;
     }>;
+    /**
+     * A `beforeSave` hook aborted the save — by returning false or throwing.
+     *
+     * Re-exposed from the embedded `ngx-dynamic-form`, and emitted by `saveSection` too. The
+     * inner form already ran the hook and already refused the save, but nothing carried that
+     * out to a host binding this component: the veto worked and looked exactly like a Save
+     * button that did nothing, which is the failure `saveRejected` exists to prevent.
+     */
+    saveRejected: EventEmitter<{
+        reason: string;
+        error?: unknown;
+    }>;
     dynamicFormComp?: DynamicFormComponent;
     private readonly rulesEvaluation;
     private readonly rbacService;
+    private readonly hookRegistry;
     private readonly host;
     private readonly injector;
     readonly currentData: i0.WritableSignal<Record<string, any>>;
@@ -1355,7 +1368,18 @@ declare class DynamicRecordFormComponent implements OnChanges {
      * validity of the tab's own controls, and rules filtered to this tab — a rule targeting
      * a hidden tab must not block the save (the reference's OV0-968 fix).
      */
-    saveSection(): void;
+    saveSection(): Promise<void>;
+    /**
+     * Put a record to the entity's `beforeSave` hook.
+     *
+     * `sectionSave` carries the *whole* record — `extractRecord()`, not the tab's slice — so
+     * the same payload reached persistence through two buttons, one of which asked the hook
+     * and one of which did not. A hook registered to veto a save is a data-integrity
+     * mechanism; having a second route around it made it advisory.
+     *
+     * @returns the record to emit, or `null` when the hook aborted (already reported).
+     */
+    private runBeforeSave;
     /**
      * Seed the session baseline from the loaded record so `VALUE_CHANGED` rules and the
      * modification banner compare against the record as it was opened — not as it was
@@ -1423,7 +1447,7 @@ declare class DynamicRecordFormComponent implements OnChanges {
      */
     jumpToField(fieldId: string): void;
     static ɵfac: i0.ɵɵFactoryDeclaration<DynamicRecordFormComponent, never>;
-    static ɵcmp: i0.ɵɵComponentDeclaration<DynamicRecordFormComponent, "ngx-dynamic-record-form", never, { "config": { "alias": "config"; "required": false; }; "rules": { "alias": "rules"; "required": false; }; "initialData": { "alias": "initialData"; "required": false; }; "userRoles": { "alias": "userRoles"; "required": false; }; "language": { "alias": "language"; "required": false; }; "readonly": { "alias": "readonly"; "required": false; }; "loading": { "alias": "loading"; "required": false; }; "error": { "alias": "error"; "required": false; }; "isReadOnly": { "alias": "isReadOnly"; "required": false; }; "readOnlyFields": { "alias": "readOnlyFields"; "required": false; }; "viewMode": { "alias": "viewMode"; "required": false; }; }, { "formSubmit": "formSubmit"; "formChange": "formChange"; "formReset": "formReset"; "sectionSave": "sectionSave"; }, never, never, true, never>;
+    static ɵcmp: i0.ɵɵComponentDeclaration<DynamicRecordFormComponent, "ngx-dynamic-record-form", never, { "config": { "alias": "config"; "required": false; }; "rules": { "alias": "rules"; "required": false; }; "initialData": { "alias": "initialData"; "required": false; }; "userRoles": { "alias": "userRoles"; "required": false; }; "language": { "alias": "language"; "required": false; }; "readonly": { "alias": "readonly"; "required": false; }; "loading": { "alias": "loading"; "required": false; }; "error": { "alias": "error"; "required": false; }; "isReadOnly": { "alias": "isReadOnly"; "required": false; }; "readOnlyFields": { "alias": "readOnlyFields"; "required": false; }; "viewMode": { "alias": "viewMode"; "required": false; }; }, { "formSubmit": "formSubmit"; "formChange": "formChange"; "formReset": "formReset"; "sectionSave": "sectionSave"; "saveRejected": "saveRejected"; }, never, never, true, never>;
 }
 
 /**
@@ -1884,7 +1908,18 @@ declare class DateFieldComponent {
     readonly: boolean;
     masked: boolean;
     get label(): string;
-    /** ISO 8601 date → locale display string (ONEHERMES convention: always UTC, display in user locale) */
+    /**
+     * ISO 8601 date → display string, through the formatter the host configured.
+     *
+     * This used to call `toLocaleDateString()` directly, which meant `setDateFormatters` — the
+     * one seam for choosing how a date is rendered — reached the record summary and the `time`
+     * field but not this one. A host that configured formatters got them almost everywhere,
+     * and silently did not get them on the field type most likely to be the reason they
+     * configured formatters at all.
+     *
+     * The default formatter is `toLocaleDateString()` with no locale, so an application that
+     * has not called `setDateFormatters` renders exactly what it rendered before.
+     */
     formatDate(value: string | null): string;
     /**
      * Resolved through `ValidationMessagesService`, so `provideNgxDynamicEntity({
@@ -1925,9 +1960,17 @@ declare class DateTimeFieldComponent {
     /** The input's local `YYYY-MM-DDTHH:mm` → stored ISO 8601 UTC. */
     onInput(value: string): void;
     /**
-     * Displays date *and* time. `DateFieldComponent` used `toLocaleDateString()` here, so a
-     * datetime read back through the field showed no time while the same value in the record
-     * summary — which goes through core's `formatDisplayValue` — showed it.
+     * Displays date *and* time, through the formatter the host configured.
+     *
+     * Two rounds of the same fault. First this called `toLocaleDateString()`, so a datetime
+     * read back through the field showed no time while the record summary showed it. Then it
+     * called `toLocaleString()` directly, which fixed the time but kept the field outside
+     * `setDateFormatters` — so a host that configured formatters still saw them apply to the
+     * summary and not to the field. Going through `formatDisplayValue` is what makes the two
+     * paths agree by construction rather than by matching literals.
+     *
+     * `parseStored` accepts shapes `new Date(raw)` alone does not, so the *parsed* instant is
+     * handed on as ISO rather than the raw value.
      */
     formatDateTime(value: unknown): string;
     /**