ngx-eiffage-material 0.0.47 → 0.0.48

package/index.d.ts

@@ -898,7 +898,7 @@ declare class NgxAlert {
     type: _angular_core.InputSignal<AlertType>;
     title: _angular_core.InputSignal<string | undefined>;
     message: _angular_core.InputSignal<string | undefined>;
-    iconName: _angular_core.Signal<"info" | "warning" | "error" | "check_circle">;
+    iconName: _angular_core.Signal<"error" | "info" | "warning" | "check_circle">;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<NgxAlert, never>;
     static ɵcmp: _angular_core.ɵɵComponentDeclaration<NgxAlert, "ngx-alert", never, { "type": { "alias": "type"; "required": false; "isSignal": true; }; "title": { "alias": "title"; "required": false; "isSignal": true; }; "message": { "alias": "message"; "required": false; "isSignal": true; }; }, {}, never, ["*"], true, never>;
 }
@@ -1041,16 +1041,23 @@ declare class NgxPaginatedSelectBottomSheetComponent<T, U extends PaginatedFilte
     readonly allSelected: _angular_core.Signal<boolean>;
     readonly someSelected: _angular_core.Signal<boolean>;
     /**
-     * Only reads `resource.value()` — never `data.filters()`.
+     * Reactively depends ONLY on `resource.value()`. The filter snapshot is read
+     * via `untracked` so external filter changes (parent-driven, e.g. an extra
+     * filters panel) do NOT create a reactive dependency here — that would make
+     * the effect re-run on scroll page increments with stale resource data,
+     * duplicating items and breaking `onScroll` (see original limitation).
      *
-     * When a query change or a new open resets to page 1 we call
-     * `accumulatedItems.set([])` synchronously *before* updating the filter,
-     * so by the time this effect fires with new data it always appends onto an
-     * already-clean array.  Reading `data.filters()` here would cause the effect
-     * to run a second time (with stale resource data) the moment the page number
-     * is incremented on scroll, duplicating items and making
-     * `options().length >= total()` so `onScroll` would never fire again.
+     * Reset logic:
+     *  - Fingerprint the current filter identity (everything except `pageNumber`).
+     *  - If the fingerprint changed since the previous fetch, this fetch belongs
+     *    to a different filter set → replace the accumulated array.
+     *  - If only `pageNumber` moved, this is a scroll-load-more → append.
+     *
+     * This is what allows callers to mutate `data.filters` from outside (extra
+     * filter selects, checkboxes, etc.) and have the list refresh cleanly
+     * without the previous page's items lingering.
      */
+    private _lastFilterFingerprint;
     private readonly _accumEffect;
     constructor();
     isSelected(item: T): boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-eiffage-material",
-  "version": "0.0.47",
+  "version": "0.0.48",
   "peerDependencies": {
     "@angular/common": "^20.1.0",
     "@angular/core": "^20.1.0"