@elasticias/screens 1.0.27 → 1.0.29

package/package.json

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

package/types/elasticias-screens.d.ts

@@ -286,6 +286,13 @@ declare abstract class AbstractScreenComponent extends AbstractComponent impleme
     refreshStaticLists(): Promise<void>;
     invalidateReference(key: string): Promise<void>;
     invalidateReferences(keys: string[]): Promise<void>;
+    /** The record the user acted on carries no id — it was removed by someone
+     *  else, the list is stale, or the route points at nothing. Say that,
+     *  rather than the internal "Item [id] is undefined!" this used to ship
+     *  to end users. Lives on the common base so every screen abstract
+     *  (search, detail and sub in V1 and V2, plus report-v2) says the same
+     *  thing — four copies of one string is how this file set drifts. */
+    protected recordNotFound(): void;
     handleErrors(errors: string[]): void;
     setServerErrors(errors: {
         [key: string]: string[];
@@ -357,6 +364,13 @@ declare abstract class AbstractDetailScreenComponent extends AbstractScreenCompo
     protected customizeDuplicatedEntity(entity: any): any;
     duplicate(): void;
     print(): void;
+    /**
+     * Name of the record being deleted, so the confirmation can say what
+     * it is about to destroy rather than asking about "this item".
+     * Override in the screen and return whatever a user recognises the
+     * record by — `return this.entity?.name;` is the usual body.
+     */
+    protected getDeleteConfirmName(): string | undefined;
     delete(): void;
     navigateBack(): void;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<AbstractDetailScreenComponent, never>;
@@ -399,6 +413,19 @@ declare abstract class AbstractSearchScreenComponent extends AbstractScreenCompo
     navigateToDetails(id?: any): void;
     add(): void;
     edit(id: any): void;
+    /**
+     * Name of the row being deleted, so the confirmation can say what it
+     * is about to destroy rather than asking about "this item". Override
+     * in the screen — look the row up in the loaded results and return
+     * whatever a user would recognise it by.
+     *
+     * ```ts
+     * protected override getDeleteConfirmName(id: any) {
+     *   return this.searchEntity.items?.find((r: any) => r.id === id)?.name;
+     * }
+     * ```
+     */
+    protected getDeleteConfirmName(_id: any): string | undefined;
     delete(id: any): void;
     duplicate(id: any): void;
     clear(): void;
@@ -826,6 +853,19 @@ declare abstract class AbstractSearchScreenV2<TItem = any> extends AbstractScree
     /** Open the create form. */
     add(): void;
     edit(id: any): void;
+    /**
+     * Name of the row being deleted, so the confirmation can say what it
+     * is about to destroy — "Delete ANDALOCY PARFUMS?" rather than
+     * "Delete?". Override in the screen; returning `undefined` keeps the
+     * generic message, which still reads correctly.
+     *
+     * ```ts
+     * protected override getDeleteConfirmName(id: any) {
+     *   return this.items().find(r => r.id === id)?.name;
+     * }
+     * ```
+     */
+    protected getDeleteConfirmName(_id: any): string | undefined;
     delete(id: any): void;
     duplicate(id: any): void;
     ngOnDestroy(): void;
@@ -1009,6 +1049,19 @@ declare abstract class AbstractDetailScreenV2<TItem extends object = any> extend
     /**
      * Soft-delete-then-navigate-back. Confirms with the user first.
      */
+    /**
+     * Name of the record being deleted, so the confirmation can say what
+     * it is about to destroy — "Delete ANDALOCY PARFUMS?" rather than
+     * "Delete?". Override in the screen; returning `undefined` keeps the
+     * generic message, which still reads correctly.
+     *
+     * ```ts
+     * protected override getDeleteConfirmName() {
+     *   return this.entity()?.name;
+     * }
+     * ```
+     */
+    protected getDeleteConfirmName(): string | undefined;
     delete(): void;
     /** Navigate to `/details/:id?mode=duplicate` so the abstract can
      *  reload the source entity, treat it as a template, and persist