@elasticias/screens 1.0.26 → 1.0.28

package/package.json

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

package/types/elasticias-screens.d.ts

@@ -357,7 +357,18 @@ 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;
+    /** The screen has no record id — it was removed by someone else, or the
+     *  route is stale. Say that, rather than the internal
+     *  "Item [id] is undefined!" this used to ship to end users. */
+    protected recordNotFound(): void;
     navigateBack(): void;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<AbstractDetailScreenComponent, never>;
     static ɵcmp: _angular_core.ɵɵComponentDeclaration<AbstractDetailScreenComponent, "ng-component", never, {}, {}, never, never, true, never>;
@@ -399,7 +410,24 @@ 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;
+    /** The row the user acted on carries no id — it was removed by someone
+     *  else, or the list is stale. Say that, rather than the internal
+     *  "Item [id] is undefined!" this used to ship to end users. */
+    protected recordNotFound(): void;
     duplicate(id: any): void;
     clear(): void;
     ngOnDestroy(): void;
@@ -826,7 +854,24 @@ 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;
+    /** The row the user acted on carries no id — it was removed by someone
+     *  else, or the list is stale. Say that, rather than the internal
+     *  "Item [id] is undefined!" this used to ship to end users. */
+    protected recordNotFound(): void;
     duplicate(id: any): void;
     ngOnDestroy(): void;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<AbstractSearchScreenV2<any>, never>;
@@ -1009,7 +1054,24 @@ 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;
+    /** The screen has no record id — it was removed by someone else, or
+     *  the route is stale. Say that, rather than the internal
+     *  "Item [id] is undefined!" this used to ship to end users. */
+    protected recordNotFound(): void;
     /** Navigate to `/details/:id?mode=duplicate` so the abstract can
      *  reload the source entity, treat it as a template, and persist
      *  via `service.create()` after the user hits Save.