@elasticias/screens 1.0.49 → 1.0.51

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elasticias/screens",
-  "version": "1.0.49",
+  "version": "1.0.51",
   "peerDependencies": {
     "@angular/common": "^21.0.0",
     "@angular/core": "^21.0.0",

package/types/elasticias-screens.d.ts

@@ -185,6 +185,34 @@ declare abstract class ScreenConfig {
      * to opt out. Must match the backend IAuditable.AuditEntityType (e.g. 'Client').
      */
     AUDIT_ENTITY_TYPE?: string;
+    /**
+     * Detail screens: translate raw values in the change-history box. Maps an
+     * audited field path to the static reference list holding its codes, e.g.
+     * `{ status: 'boutique_order_status' }` (key `status` also covers the
+     * from/to of status-change entries). The lists are loaded with the screen
+     * (no need to repeat them in DETAILS_STATIC_LISTS); bind
+     * `<ef-change-history [entries]="auditEntries()" [valueLists]="auditValueLists()" />`.
+     * Unset keeps raw values.
+     */
+    AUDIT_VALUE_LISTS?: Record<string, string>;
+    /**
+     * Detail screens: business-rule codes (422 `ruleCode`) meaning "the record
+     * changed since you loaded it", e.g. ERP `['BR_SO_0123']`. A failed update
+     * with one of them offers a "reload" confirm; accepting
+     * reloads the record and drops the unsaved edits. The app must define the
+     * i18n keys `ef_stale_reload` (button), `ef_stale_reload_confirm` (message,
+     * say that unsaved edits are lost) and `ef_stale_reload_header`.
+     */
+    STALE_RULE_CODES?: string[];
+    /**
+     * Detail screens: after a successful in-place update (not a create or
+     * duplicate) refresh the record, so server-owned fields such as a
+     * concurrency revision are current for the next save. Uses the update
+     * response when it is the saved record (an object whose `id` is the
+     * screen's entity id), otherwise one `get(id)`. Change history reloads
+     * either way. Default false: the record is left as edited.
+     */
+    RELOAD_AFTER_SAVE?: boolean;
     /**
      * Report screens (AbstractReportScreenV2): starting period preset for the
      * screen's ef-datepicker-advanced. Unset → 'last_30_days'.
@@ -904,6 +932,13 @@ declare abstract class AbstractSearchScreenV2<TItem = any> extends AbstractScree
      * criteria to cache on success so revisits can restore.
      */
     search(): void;
+    /**
+     * Hook for a screen whose search returns more than a page of rows (counts,
+     * facets, a summary): called with the raw response after `items` and
+     * `totalCount` are set, for the latest issued search only. A stale or
+     * failed search never reaches it.
+     */
+    protected afterSearch(_result: unknown): void;
     setSearchText(text: string): void;
     setPage(pageNumber: number, pageSize?: number): void;
     setSort(field: string, direction?: string): void;
@@ -1058,6 +1093,14 @@ interface EfDetailToolbarAction {
      * context with no write state (no `canWrite`) leaves the action shown.
      */
     requiresWrite?: boolean;
+    /**
+     * On a phone, when the actions overflow into the menu, this one stays
+     * inline beside Save (a screen's next step, which should never be one
+     * tap deeper). Filtering by `visible`, `permission` and `requiresWrite`
+     * still applies first. Ignored on tablet and desktop, which never
+     * overflow. Keep it to one action: each one kept takes row width.
+     */
+    keepInView?: boolean;
     /** Click handler. */
     command?: () => void;
 }
@@ -1130,6 +1173,12 @@ declare abstract class AbstractDetailScreenV2<TItem extends object = any> extend
      * `<ef-change-history [entries]="auditEntries()" />`.
      */
     readonly auditEntries: _angular_core.WritableSignal<any[]>;
+    /**
+     * Field path to reference items for `<ef-change-history [valueLists]>`,
+     * built from `ScreenConfig.AUDIT_VALUE_LISTS` and the already-loaded static
+     * lists. Empty (raw values) when the config does not declare any.
+     */
+    readonly auditValueLists: _angular_core.Signal<Record<string, any[]>>;
     /** Loaded entity. Empty object when on `/details` (create mode). */
     readonly entity: _angular_core.WritableSignal<TItem>;
     /** PK from the route param, or `null` on `/details` (new). */
@@ -1208,6 +1257,8 @@ declare abstract class AbstractDetailScreenV2<TItem extends object = any> extend
     patchEntity(patch: Partial<TItem>): void;
     /** Fetch the entity from the backend and populate `entity`. */
     loadData(): void;
+    /** Install a fetched (or save-returned) record as the current entity. */
+    private applyLoaded;
     /**
      * Persist the entity. Routes to `service.create()` when in new
      * or duplicate mode, `service.update(id, entity)` when editing.
@@ -1218,6 +1269,23 @@ declare abstract class AbstractDetailScreenV2<TItem extends object = any> extend
      * anyway.
      */
     save(): void;
+    /**
+     * True when a failed save means the record changed since it was loaded:
+     * a refusal whose `ruleCode` is in the config's `STALE_RULE_CODES`. A bare
+     * 409 is a duplicate (e.g. a slug already taken), not a stale record, so
+     * it never offers a reload. Only a refusal
+     * the app's interceptor already toasted counts, so the user is never
+     * told twice.
+     */
+    protected isStaleSave(error: unknown): boolean;
+    /**
+     * Asks, in an accessible confirm dialog (focus trapped, Escape cancels),
+     * whether to reload the record. Accepting discards the unsaved edits,
+     * and the message says so. The refusal itself was already toasted.
+     * App keys: `ef_stale_reload` (button), `ef_stale_reload_confirm`
+     * (message) and optionally `ef_stale_reload_header`.
+     */
+    protected offerStaleReload(): void;
     /**
      * Soft-delete-then-navigate-back. Confirms with the user first.
      */