@masterteam/client-components 0.0.96 → 0.0.97

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@masterteam/client-components",
-  "version": "0.0.96",
+  "version": "0.0.97",
   "publishConfig": {
     "directory": "../../../dist/masterteam/client-components",
     "linkDirectory": true,
@@ -16,9 +16,9 @@
     "rxjs": "^7.8.2",
     "tailwindcss": "^4.2.2",
     "tailwindcss-primeui": "^0.6.1",
-    "@masterteam/forms": "^0.0.156",
+    "@masterteam/forms": "^0.0.157",
     "@masterteam/icons": "^0.0.17",
-    "@masterteam/components": "^0.0.301",
+    "@masterteam/components": "^0.0.302",
     "@masterteam/dashboard-builder": "^0.0.92"
   },
   "dependencies": {

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

@@ -170,6 +170,9 @@ interface ClientListTableDisplayConfig {
      * The key must name a column that is actually rendered, and grouping only
      * makes sense once every row of a group is loaded — with backend paging a
      * group is split across pages and each page grows its own header.
+     *
+     * Also the board's starting grouping: table and cards share one toolbar
+     * state per list, seeded once by whichever view renders first.
      */
     groupBy?: string;
 }
@@ -245,7 +248,13 @@ interface ClientListFormConfiguration extends ClientListBaseConfiguration {
     table?: ClientListTableDisplayConfig;
     /**
      * Host hook to reshape built columns/rows before render — see
-     * {@link ClientListTableTransform}. Applies to `table` area only.
+     * {@link ClientListTableTransform}.
+     *
+     * On `areaType: 'cards'` it runs over each card's row representation, so a
+     * board offers the same columns the table does — which is what lets
+     * `table.groupBy` name a host-derived column and still group a board. Cells
+     * the transform *adds* become row-only fields (grouping, filters, export);
+     * the card face keeps rendering its own layout and never shows them.
      */
     transformResult?: ClientListTableTransform;
 }
@@ -808,6 +817,22 @@ declare class ClientListStateService {
     setInformativeResult(key: string, response: ClientListInformativeDashboardPayload | null, config: NormalizedClientListConfiguration): void;
     toggleExpanded(key: string): void;
     private mergeItemState;
+    /**
+     * Runs the host's `transformResult` over a board, so it offers the same
+     * columns the table of the same list does — the ones a host derives
+     * included (a descendant list's level and owning record, say). That is what
+     * lets a board group, filter and export by them, and what lets a
+     * `table.groupBy` default naming a derived column group a board at all.
+     *
+     * The card face is left alone: the card keeps rendering its own layout, and
+     * the derived cells ride on `displayProperties`, which only the card's row
+     * representation reads. Cells the transform rewrote rather than added are
+     * not carried over — the card already shows those fields its own way.
+     *
+     * Without a transform the board keeps its old behaviour: no `columns`, so
+     * the view derives them from the first card's entities.
+     */
+    private shapeCards;
     private toCards;
     private orderRecords;
     private resolvePrimarySchema;