@elasticias/ui 1.0.27 → 1.0.28

package/package.json

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

package/types/elasticias-ui.d.ts

@@ -4407,6 +4407,11 @@ type EfTableDensity = 'compact' | 'default' | 'comfortable';
  * 2. **`tbl-head-info` / `tbl-head-actions` slots**: still projected
  *    so the consumer can render the count text + density / columns /
  *    view-toggle buttons next to the table header.
+ * 3. **`[loading]` is not optional.** Bind the screen's own loading
+ *    signal: without it the card can't tell "still fetching" from
+ *    "nothing to fetch" and greets a waiting user with the empty
+ *    state. While loading with no rows yet it shimmers `ef-skeleton`
+ *    rows (table and mobile list alike) and flags `aria-busy`.
  *
  * ```html
  * <ef-data-card
@@ -4499,10 +4504,27 @@ declare class EfDataCardComponent<TRow = any> implements AfterContentInit {
     readonly hidePager: _angular_core.InputSignalWithTransform<boolean, unknown>;
     /** Currently active sort. Header click toggles asc / desc. */
     readonly sort: _angular_core.InputSignal<EfDataCardSort>;
+    /**
+     * First load and every refresh. While true with no rows yet, the body
+     * shimmers `ef-skeleton` placeholders instead of the empty state — a
+     * list that is still loading must never say "nothing here yet". A
+     * refresh that already has rows (paging, sorting, filtering) keeps
+     * them on screen rather than blanking the table; either way the row
+     * container is flagged `aria-busy`, as `ef-card` does.
+     */
     readonly loading: _angular_core.InputSignalWithTransform<boolean, unknown>;
     /** Empty string = no error. Non-empty triggers an error chip in tbl-head. */
     readonly errorMsg: _angular_core.InputSignal<string>;
     readonly loadingKey: _angular_core.InputSignal<string>;
+    /**
+     * Placeholder rows drawn while the first load is in flight. The page
+     * size is what the operator is about to get, so it sets the height —
+     * clamped so a 100-per-page list doesn't shimmer a full screen of
+     * bars, and a 5-per-page one still reads as a list.
+     */
+    readonly skeletonLines: _angular_core.Signal<number[]>;
+    /** First load: nothing to show yet, so the rows are placeholders. */
+    readonly showSkeleton: _angular_core.Signal<boolean>;
     /**
      * When `true`, double-clicking anywhere on a `<tr>` emits the row
      * via `rowDoubleClick` and the body rows render with