@masterteam/client-components 0.0.66 → 0.0.68

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@masterteam/client-components",
-  "version": "0.0.66",
+  "version": "0.0.68",
   "publishConfig": {
     "directory": "../../../dist/masterteam/client-components",
     "linkDirectory": true,
@@ -16,10 +16,10 @@
     "rxjs": "^7.8.2",
     "tailwindcss": "^4.2.2",
     "tailwindcss-primeui": "^0.6.1",
-    "@masterteam/forms": "^0.0.126",
-    "@masterteam/icons": "^0.0.17",
-    "@masterteam/dashboard-builder": "^0.0.68",
-    "@masterteam/components": "^0.0.238"
+    "@masterteam/forms": "^0.0.127",
+    "@masterteam/components": "^0.0.241",
+    "@masterteam/dashboard-builder": "^0.0.69",
+    "@masterteam/icons": "^0.0.17"
   },
   "dependencies": {
     "tslib": "^2.8.1"

package/types/masterteam-client-components-client-list.d.ts

@@ -138,14 +138,28 @@ interface ClientListFormConfiguration extends ClientListBaseConfiguration {
     mode?: ClientListMode;
     columnKeys?: string[];
     /**
-     * Defaults to true. Paginated tables use backend page/pageSize requests and
-     * render a paginator. Set false only for bounded local datasets that should
-     * render through virtual scroll.
+     * `areaType: 'table'` — defaults to true. Paginated tables use backend
+     * page/pageSize requests and render a paginator. Set false only for
+     * bounded local datasets that should render through virtual scroll.
+     *
+     * `areaType: 'cards'` — defaults to false (the full record set is fetched
+     * in one call, preserving pre-existing behavior). Set true to opt into
+     * backend-paginated cards, fetched page by page and appended as the user
+     * scrolls (infinite scroll) instead of loading every record up front.
+     *
+     * Note for cards: this flag used to be ignored entirely — cards always
+     * fetched everything regardless of what was configured. A cards config
+     * that already carries `isPaginated: true` (copied from a table config,
+     * or a config object shared across area types) therefore changes
+     * behaviour: it now pages. Requires backend support for `page`/`pageSize`
+     * on the `Card` projection; without a `pagination` block in the response
+     * the list degrades to the first page only.
      */
     isPaginated?: boolean;
     /**
      * Backend page size when `isPaginated` is true. For local virtual-scroll
-     * tables (`isPaginated: false`), this is the explicit fetch cap.
+     * tables (`isPaginated: false`), this is the explicit fetch cap. Ignored
+     * for cards when `isPaginated` is false.
      */
     take?: number;
     /**
@@ -459,7 +473,20 @@ declare class ClientListStateService {
     setError(key: string, message: string | null): void;
     setTablePaging(key: string, skip: number, take: number): void;
     setRowsResult(key: string, response: RuntimeTableRowsResponse, config: NormalizedClientListConfiguration, skip: number, take: number): void;
-    setCardsResult(key: string, response: ClientListCardsPayload, config: NormalizedClientListConfiguration): void;
+    setCardsResult(key: string, response: ClientListCardsPayload, config: NormalizedClientListConfiguration, skip?: number, take?: number, append?: boolean): void;
+    /**
+     * Appends `next` to `current`, dropping any card whose id is already
+     * present. Ids are the grid's `@for` track key, so duplicates are a runtime
+     * error, not a cosmetic issue.
+     */
+    private concatDistinctCards;
+    /**
+     * The page size the backend actually applied, falling back to the size we
+     * asked for. Returns `0` when neither is usable — i.e. the response carried
+     * no paging contract, so there is no stride to walk and the caller should
+     * treat the set as complete.
+     */
+    private resolveEffectivePageSize;
     setInformativeResult(key: string, response: ClientListInformativeDashboardPayload | null, config: NormalizedClientListConfiguration): void;
     toggleExpanded(key: string): void;
     private mergeItemState;
@@ -501,6 +528,19 @@ declare class ClientList implements OnDestroy {
     private readonly runtimeFilters;
     constructor();
     onLazyLoad(itemKey: string, event: ClientListLazyLoadEvent): void;
+    /**
+     * Fetches the next page of cards and appends it to the currently loaded
+     * set — the infinite-scroll counterpart to table pagination. No-op unless
+     * `isPaginated` is enabled for this cards list, a load is already in
+     * flight, or every record has already been loaded.
+     *
+     * The offset comes from `item.skip`, which the state service advances by
+     * the page size the backend actually applied. Deriving it from
+     * `cards.length` instead would drift the moment a page came back short (a
+     * capped `pageSize`, a de-duplicated overlap) and re-request a page we
+     * already hold.
+     */
+    loadMoreCards(itemKey: string): void;
     reload(itemKey?: string): void;
     reloadByKey(itemKey: string): void;
     toggleExpanded(key: string): void;
@@ -583,7 +623,7 @@ declare class ClientListApiService {
     private readonly runtimeFetchBaseUrl;
     private readonly informativeBaseUrl;
     getRows(contextKey: ClientListRuntimeContext, query: ClientListTableQuery, filters?: ClientListFetchRequestFilter[]): Observable<Response<RuntimeTableRowsResponse>>;
-    getCards(contextKey: ClientListRuntimeContext, filters?: ClientListFetchRequestFilter[]): Observable<Response<ClientListCardsPayload>>;
+    getCards(contextKey: ClientListRuntimeContext, filters?: ClientListFetchRequestFilter[], skip?: number, take?: number): Observable<Response<ClientListCardsPayload>>;
     getInformativeDashboard(levelId: number, moduleId: number): Observable<Response<ClientListInformativeDashboardPayload>>;
     private queryRuntime;
     private resolveTablePropertyKeys;