@mintplayer/ng-spark 22.28.0 → 22.29.0

package/types/mintplayer-ng-spark-grid.d.ts

@@ -430,6 +430,11 @@ export declare class SparkQueryGridComponent {
   offersCreate: import("@angular/core").Signal<boolean>;
   visibleCustomActions: import("@angular/core").Signal<CustomActionDefinition[]>;
   fetchFn: import("@angular/core").WritableSignal<BsDatatableFetch<QueryResultItem> | null>;
+  /**
+   * The grid's own datatable, for {@link reload}. A `viewChild` is safe here: the `@if` concern above
+   * is about hosts holding this grid, while this is the grid's own template, read only on demand.
+   */
+  private readonly datatable;
   /**
    * Why the component renders its own failure instead of only reporting one.
    *
@@ -563,8 +568,15 @@ export declare class SparkQueryGridComponent {
    * Data-level on purpose: it re-seeds the fetch closure and nothing else. For a definition
    * change — new columns, a renamed query — the inputs themselves must change; that is the
    * expensive path. Inert when rows come from the host: there is nothing here to re-run.
+   *
+   * Through the datatable's own `reload()` (mintplayer-ng-bootstrap#407), which re-queries the
+   * current page and coalesces calls within a microtask. Swapping the `[fetch]` identity, the only
+   * way before it existed, also disarmed the datatable's reload dedupe. The swap stays as the
+   * fallback while the datatable is not rendered (loading), where a fresh closure is what counts.
    */
-  reload(): void;
+  reload(options?: {
+    resetPage?: boolean;
+  }): void;
   private onSearchChanged;
   /**
    * Replaces the fetched columns only when they actually differ.
@@ -627,11 +639,13 @@ export declare class SparkQueryGridComponent {
    */
   protected onFilterChange(detail: FilterChangeDetail): void;
   /**
-   * Back to page 1 and a fresh fetch identity, exactly as a new search term does.
+   * Back to page 1 and a forced re-fetch.
    *
    * Both halves matter: the old page number means nothing against a different result set, and the
    * datatable dedupes reloads by `(page, perPage, sort)` — none of which a filter changes — so
-   * without a new fetch identity the request is silently never made.
+   * without forcing it the request is silently never made. `resetPage` makes the datatable fetch
+   * page 1 itself: the settings binding reaches it only on the next change detection, after the
+   * reload already fetched.
    */
   private onFilterChanged;
   /**