Merge pull request #5 from lemerv/develop

Column Summaries feature and other fixes

Author: lemerv

.prettierignore

@@ -8,4 +8,5 @@
 .sf
 .vscode
 
-coverage/
+coverage/
+repomix-output.xml

README.md

@@ -20,6 +20,7 @@ Kanban Explorer is a Lightning Web Component that transforms your Salesforce rec
 - **Context-aware** - works on record pages, app pages, and home pages
 - **Multiple data modes** - parent mode (single select and multi select), parentless mode, and record page mode
 - **Flexible customization** - configurable fields, filters, search, and sorting
+- **Column summaries** - configure up to 3 column summaries, such as SUMs, AVGs, COUNTs, and more
 - **Visual goodies** - add icons and emojis to cards
 
 ## Quick Start
@@ -72,6 +73,7 @@ Kanban Explorer is adaptable:
 - **Date Formatting**: Custom date/time display formats
 - **Field Labels**: Toggle field labels on/off for cleaner interfaces
 - **Card Counts**: Display record counts per column
+- **Column summaries**: Show up to 3 per-column metrics (SUM, AVG, MIN, MAX, COUNT_TRUE, COUNT_FALSE) for numeric, date, and checkbox fields
 
 ### 🔒 Safe and Secure
 

config/project-scratch-def.json

@@ -11,6 +11,11 @@
     "FieldAuditTrail"
   ],
   "settings": {
+    "userSettings": {
+      "language": "en_US",
+      "locale": "en_AU",
+      "timeZone": "Australia/Sydney"
+    },
     "communitiesSettings": {
       "enableNetworksEnabled": true
     },

docs/admin-guide.md

@@ -4,6 +4,7 @@
   - [Card Record Configuration](#card-record-configuration)
   - [Parent Record Configuration](#parent-record-configuration)
   - [Card Sort, Filter, and Search Configuration](#card-sort-filter-and-search-configuration)
+  - [Column Summaries Configuration](#column-summaries-configuration)
   - [Other Configuration Fields](#other-configuration-fields)
 - [Best Practices](#best-practices)
 - [Common Configuration Patterns](#common-configuration-patterns)
@@ -229,6 +230,25 @@ Use these configuration fields to control _which_ Parent records are available i
 - **Example**: `Subject,Description,CaseNumber,Account.Name`
 - **Tip**: Search works for a field that isn't actually displayed on the board
 
+## Column Summaries Configuration
+
+### Column Summaries Definition <!-- omit from toc -->
+
+- **Property**: `Column Summaries Definition`
+- **Purpose**: Define up to three summaries that appear in each column header.
+- **Format**: `[FieldApiName|SUMMARY_TYPE|Label]` entries separated by semicolons
+- **Summary Types**: `SUM`, `AVG`, `MIN`, `MAX`, `COUNT_TRUE`, `COUNT_FALSE`
+- **Examples**:
+  - `[Amount|SUM|Total Amount];[Amount|AVG|Avg Amount]`
+  - `[CloseDate|MIN|Earliest Close];[CloseDate|MAX|Latest Close]`
+  - `[IsEscalated|COUNT_TRUE|Escalated];[IsEscalated|COUNT_FALSE|Not Escalated]`
+- **Notes**:
+  - `SUM`/`AVG` require numeric fields (Number, Currency, Percent, Integer, Double)
+  - `MIN`/`MAX` allow numeric or Date/DateTime fields
+  - `COUNT_TRUE`/`COUNT_FALSE` require Checkbox fields
+  - If a currency summary contains multiple currencies in the same column, the summary value is blocked and shows `Mixed currencies`, and a warning banner is displayed
+  - Invalid definitions are ignored and surfaced as a non-blocking warning
+
 ## Other Configuration Fields
 
 #### Empty Group Label <!-- omit from toc -->
@@ -243,9 +263,11 @@ Use these configuration fields to control _which_ Parent records are available i
 - **Purpose**: Custom date/time display format
 - **Format**: Java SimpleDateFormat pattern
 - **Examples**:
-  - `dd/MM/yyyy h:mm a` (default)
+  - `dd/MM/yyyy h:mm a`
   - `MM-dd-yy HH:mm`
   - `EEEE, MMMM d, yyyy`
+- **Notes**:
+  - Leave blank to use the running user's Salesforce locale settings
 
 #### Debug Logging <!-- omit from toc -->
 

force-app/main/default/lwc/lresDateTimeUtils/__tests__/lresDateTimeUtils.test.js

@@ -40,6 +40,21 @@ describe("lresDateTimeUtils", () => {
       expect(result).toBe("2023-12-25 14:30:45");
     });
 
+    test("should drop time tokens for date-only fields", () => {
+      const result = formatValueWithPattern(TEST_DATE_ONLY_STRING, {
+        pattern: "yyyy-MM-dd HH:mm:ss",
+        dateOnly: true
+      });
+      expect(result).toBe("2023-12-25");
+    });
+
+    test("should append time tokens for datetime fields when missing", () => {
+      const result = formatValueWithPattern(TEST_DATE, {
+        pattern: "yyyy-MM-dd"
+      });
+      expect(result).toBe("2023-12-25 2:30 PM");
+    });
+
     test("should format date string with date-only pattern", () => {
       const result = formatValueWithPattern(TEST_DATE_ONLY_STRING, {
         pattern: "MM/dd/yyyy",
@@ -69,11 +84,12 @@ describe("lresDateTimeUtils", () => {
       expect(result).toBeNull();
     });
 
-    test("should return null for invalid pattern", () => {
+    test("should fall back to locale formatting when pattern is missing", () => {
       const result = formatValueWithPattern(TEST_DATE, {
         pattern: null
       });
-      expect(result).toBeNull();
+      expect(result).toBeDefined();
+      expect(typeof result).toBe("string");
     });
 
     test("should handle custom locale and timezone", () => {
@@ -91,7 +107,7 @@ describe("lresDateTimeUtils", () => {
         pattern: "yyyy-MM-dd HH:mm:ss",
         dateOnly: true
       });
-      expect(result).toBe("2023-12-25 00:00:00");
+      expect(result).toBe("2023-12-25");
     });
 
     test("should use pattern token cache", () => {
@@ -100,8 +116,8 @@ describe("lresDateTimeUtils", () => {
         pattern: "yyyy-MM-dd",
         patternTokenCache: cache
       });
-      expect(result).toBe("2023-12-25");
-      expect(cache.size).toBe(1);
+      expect(result).toBe("2023-12-25 2:30 PM");
+      expect(cache.size).toBe(2);
     });
   });
 
@@ -565,7 +581,7 @@ describe("lresDateTimeUtils", () => {
       const result = formatValueWithPattern(leapYearDate, {
         pattern: "yyyy-MM-dd"
       });
-      expect(result).toBe("2024-02-29");
+      expect(result).toBe("2024-02-29 12:00 PM");
     });
 
     test("should handle end of year date", () => {
@@ -637,7 +653,7 @@ describe("lresDateTimeUtils", () => {
       const result = formatValueWithPattern(TEST_DATE, {
         pattern: "MMM dd, yyyy"
       });
-      expect(result).toBe("Dec 25, 2023");
+      expect(result).toBe("Dec 25, 2023 2:30 PM");
     });
 
     test("should format for API requests", () => {