@wix/auto-patterns 1.26.0 → 1.28.0

package/dist/docs/auto-patterns-guide.md

@@ -167,6 +167,7 @@ export interface AppConfig {
             reflectQueryInUrl?: boolean; // Reflects query state (search, filters, sorting) in the browser URL. Default: false
             selectAllScope?: 'page' | 'all'; // Controls "Select All" scope. 'all' selects entire collection, 'page' selects only visible items. Default: 'all'
             selectionUpdateMode?: 'preserve' | 'clear'; // Controls selection behavior when data changes. 'preserve' maintains selections, 'clear' clears them. Default: 'clear'
+            paginationMode?: 'cursor' | 'offset'; // Controls pagination strategy and expected find() return shape. 'cursor' => { items, cursor, total? }, 'offset' (default) => { items, hasNext, total? }
           };
           filters?: {
             panelTitle?: string; // Title of the filters panel
@@ -803,7 +804,7 @@ Custom collection page actions execute JavaScript code that you define for colle
    ```typescript
    import { CustomActionCollectionPageActionResolver } from '@wix/auto-patterns';
    import React from 'react';
-   import { Download } from '@wix/ui-icons-common';
+   import { Download } from '@wix/wix-ui-icons-common';
 
    // IMPORTANT: Function name MUST match the action id in your configuration
    export const exportCollection: CustomActionCollectionPageActionResolver = (params) => {
@@ -923,16 +924,7 @@ Row click actions are configured at the table level using the `onRowClick` prope
 
 ⚠️ **CRITICAL**: When you configure `onRowClick` in your TypeScript configuration, you MUST provide a complete working implementation. The Auto Patterns framework cannot function without it.
 
-Custom row click actions use the `CustomActionCollectionPageActionOnRowClickResolver` type and MUST return a `ResolvedAction` object with all required properties:
-
-#### Required Return Object Structure:
-```typescript
-return {
-  label: string,        // REQUIRED: Action label
-  icon: ReactElement,   // REQUIRED: Icon component
-  onClick: () => void   // REQUIRED: Click handler function
-};
-```
+Custom row click actions use the `CustomActionCollectionPageActionOnRowClickResolver` type and MUST return a `ResolvedAction`. See [ResolvedAction Reference](./resolved_action.md) for complete field documentation.
 
 #### Complete Implementation Example:
 
@@ -1092,7 +1084,7 @@ export const quickToggle: CustomActionCollectionPageActionOnRowClickResolver = (
 - **MANDATORY IMPLEMENTATION**: If you configure `onRowClick` in TypeScript configuration, you MUST provide a complete working implementation - the framework cannot function without it
 - The action `id` in the configuration MUST exactly match the function name exported from your actions folder
 - The implementation must use the `CustomActionCollectionPageActionOnRowClickResolver` type
-- **Required Return Object**: Must return an object with `label`, `icon`, and `onClick` properties - all are required
+- **Required Return Object**: Must return a `ResolvedAction` object - see [ResolvedAction Reference](./resolved_action.md)
 - Access the clicked item's data through `actionParams.item`
 - The implementation must be exported as a named export and registered in your `PatternsWizardOverridesProvider`
 - When `onRowClick` is configured, the default navigation to entity page is completely disabled
@@ -1244,19 +1236,25 @@ export interface SchemaConfig {
     update: (updatedEntity: any) => Promise<any>;
     delete: (entityId: string) => Promise<any>;
     bulkDelete: (entityIds: string[]) => Promise<any>;
+    // The return shape depends on pagination mode (see AppConfig.collection.paginationMode)
+    // - Cursor mode: { items, cursor, total? }
+    // - Offset mode (default): { items, hasNext, total? }
     find: (
       query: Query,
       options?: {
         searchableFieldIds?: string[];
         filterFieldMapping?: Record<string, { fieldId: string }>;
       },
-    ) => Promise<{ items: any[]; total: number }>;
+    ) => Promise<
+      | { items: any[]; cursor?: string | null; total?: number | null }
+      | { items: any[]; hasNext?: boolean; total?: number | null }
+    >;
   };
 }
 
 export interface Query {
   limit: number;                    // Maximum number of items to return per request (controls page size)
-  offset: number;                   // Number of items to skip from the beginning (for pagination)
+  offset?: number;                   // Number of items to skip from the beginning (for pagination)
   page: number;                     // Current page number (1-based, works with limit for pagination)
   search?: string;                  // Text search query applied to searchable fields
   cursor?: string | null;           // Cursor-based pagination token (alternative to offset-based pagination)
@@ -1355,7 +1353,9 @@ export type Field = ReferenceField | NonReferenceField;
   - `query`: Query object with pagination, filtering, sorting, and search criteria (see Query Interface section)
   - `options.searchableFieldIds`: Array of field IDs that support text search
   - `options.filterFieldMapping`: Maps filter IDs to actual field IDs for complex filtering
-  - Returns: `{ items: any[], total: number }`
+  - Returns (depends on pagination mode):
+    - Cursor mode: `{ items: any[]; cursor?: string | null; total?: number | null }`
+    - Offset mode (default): `{ items: any[]; hasNext?: boolean; total?: number | null }`
 
 ### Field Type Information
 
@@ -1843,11 +1843,8 @@ Custom bulk actions execute JavaScript code that you define for bulk operations.
    - Be registered in the `actions` property of your `PatternsWizardOverridesProvider`
    - Follow JavaScript identifier naming rules (camelCase recommended)
 
-2. The implementation must return an object with:
-   - `label`: Text displayed for the action
-   - `icon`: An Icon component from "@wix/wix-ui-icons-common"
-   - `onClick`: Handler function for the bulk action
-   - `hidden` (optional): Boolean to hide the action when true
+2. The implementation must return a `ResolvedAction`:
+   For complete field documentation, see [ResolvedAction Reference](./resolved_action.md).
 
 3. The implementation must:
    - Use the correct type: `CustomBulkActionsActionResolver`
@@ -2470,7 +2467,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 
   return {
     label: 'My More Action',
-    icon: <MyIcon />, // optional
+    icon: <MyIcon />, // required
     onClick: () => {
       // Your custom logic here
     },
@@ -2490,7 +2487,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 - The implementation must use the `CustomEntityPageActionResolver` type.
 - The implementation must be exported as a named export (not default export).
 - The function receives `{ actionParams, sdk }` as parameters.
-- The returned object must include at least a `label` and an `onClick` handler (optionally an `icon`).
+- The returned object must be a `ResolvedAction`. See [ResolvedAction Reference](./resolved_action.md) for complete documentation.
 
 ---
 
@@ -2501,7 +2498,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 ✓ Custom actions match implementations in overrides
 ✓ The resolver is exported and registered in the `actions` property of your `PatternsWizardOverridesProvider`
 ✓ The function signature matches `CustomEntityPageActionResolver`
-✓ The returned object includes `label`, `onClick`, and optionally `icon`
+✓ The returned object is a `ResolvedAction` (see [ResolvedAction Reference](./resolved_action.md))
 
 ---
 
@@ -2608,7 +2605,7 @@ View mode actions follow the same resolver patterns as collection page actions:
 These actions are handled automatically by the AutoPatterns framework using the configuration provided.
 
 ### For Custom Actions
-Custom actions require resolver implementations:
+Custom actions require resolver implementations that return a `ResolvedAction` object. See [ResolvedAction Reference](./resolved_action.md) for complete field documentation.
 
 ```typescript
 import { CustomEntityPageActionResolver } from '@wix/auto-patterns/types';
@@ -2619,7 +2616,7 @@ export const duplicateProduct: CustomEntityPageActionResolver = (params) => {
   const schema = sdk.getSchema(sdk.collectionId);
   return {
     label: 'Duplicate Product',
-    icon: <DuplicateIcon />, // optional
+    icon: <DuplicateIcon />, // required
     onClick: async () => {
       // Your custom duplication logic here
       await schema.actions.create({
@@ -2650,6 +2647,115 @@ export const duplicateProduct: CustomEntityPageActionResolver = (params) => {
 
 ---
 
+# ResolvedAction: Common Return Type for Custom Actions
+
+All custom action resolvers in Auto Patterns must return a `ResolvedAction`. This applies to:
+- Collection page actions (primary, secondary, menus) and `onRowClick`
+- Entity page actions (view mode: primary/secondary/more; edit mode: moreActions)
+- Bulk action toolbar actions
+- Action Cell actions
+
+## Type Definition
+
+From `@wix/auto-patterns`:
+
+```typescript
+export interface ResolvedAction {
+  label: string;
+  icon: IconElement;
+  onClick: () => void;
+  disabled?: boolean;
+  hidden?: boolean;
+  tooltip?: string;
+  skin?: string;
+}
+```
+
+## Field Reference
+
+### Required Fields
+
+- **`label`** (string): Text displayed in the button or menu item.
+- **`icon`** (IconElement): An icon component, typically from `@wix/wix-ui-icons-common`. Example: `icon: <Delete />`.
+- **`onClick`** (function): Handler function invoked when the user triggers the action. Can be async.
+
+### Optional Fields
+
+- **`disabled`** (boolean): When `true`, renders the action as disabled. Pair with `tooltip` to explain why the action is unavailable.
+- **`hidden`** (boolean): When `true`, the action is completely omitted from the UI. Useful for permission-based or state-based visibility control.
+- **`tooltip`** (string): Tooltip text displayed on hover. Especially useful when the action is disabled.
+- **`skin`** (string): Visual style of the action button. Availability may vary by placement context. Recommended values:
+  - Primary actions: `"standard"`, `"inverted"`, `"premium"`
+  - Secondary/more/menu items: `"dark"`, `"destructive"`, `"premium"`
+  - If unsure, omit `skin` or use `"standard"` for primary actions and `"dark"` for secondary actions.
+
+## Examples
+
+### Minimal Example
+
+```typescript
+import { Add } from '@wix/wix-ui-icons-common';
+
+return {
+  label: 'Create',
+  icon: <Add />,
+  onClick: () => {
+    // Your action logic here
+  }
+};
+```
+
+### Complete Example with State Control
+
+```typescript
+import { Download } from '@wix/wix-ui-icons-common';
+
+return {
+  label: 'Export',
+  icon: <Download />,
+  onClick: async () => {
+    try {
+      // Perform export logic using SDK
+      await performExport();
+    } catch (error) {
+      // Handle errors, show toast, etc.
+    }
+  },
+  disabled: total === 0,
+  tooltip: total === 0 ? 'Select at least one item to export' : undefined,
+  hidden: !userHasExportPermission,
+  skin: 'premium'
+};
+```
+
+## Context-Specific Notes
+
+### Collection Page Actions
+- **onRowClick**: Access clicked item data via `actionParams.item`
+- **Collection-level actions**: Access collection context via `actionParams.collectionId`
+
+### Entity Page Actions
+- **View/Edit mode**: Access entity data via `actionParams.entity`
+- **Edit mode only**: Access form instance via `actionParams.form`
+
+### Bulk Actions
+- **Selection data**: Use `actionParams.selectedValues` and `actionParams.total`
+- **State control**: Commonly use `disabled: selectedValues.length === 0`
+
+### Action Cell Actions
+- **Row context**: Access item and position via `actionParams.item` and `actionParams.index`
+
+## See Also
+
+- [Collection Page Actions](./collection_page_actions.md)
+- [Entity Page Actions](./entity_page_actions.md) (edit mode)
+- [Entity Page View Actions](./entity_page_view_actions.md)
+- [Bulk Actions Toolbar](./bulk_actions.md)
+- [Action Cell](./action_cell.md)
+- [App Config Structure](./app_config_structure.md) (action item `skin` property)
+
+---
+
 # Installation & Setup
 
 ## 1. Install Packages
@@ -2736,6 +2842,7 @@ export default withDashboard(Index);
 
 - **Custom overrides are restricted to the defined areas only** - attempting to override or modify any other aspect of `AutoPatternsApp` is prohibited and can cause unexpected behavior
 - **Always verify override implementation** - when implementing custom overrides, you MUST ensure they are correctly imported and passed to the `PatternsWizardOverridesProvider`
+- **CRITICAL: Error handling for custom actions** - Custom actions that make external API calls (using `fetch()`, `axios`, etc.) should NOT use `errorHandler.withErrorHandler`. Only Wix HTTP requests (httpClient from @wix/essentials, Wix APIs like wix/data and wix/stores, and httpClient.fetchWithAuth()) require errorHandler wrapping. See the "Error Handling for HTTP Requests" section for details.
 
 The `PatternsWizardOverridesProvider` allows you to inject custom code to override default behaviors or add additional functionality. Below are the areas where overrides can be applied:
 
@@ -3542,22 +3649,7 @@ When implementing custom data sources, you need to map your data source field ty
 - **Reference fields** → `'REFERENCE'`
 - **URL fields** → `'URL'`
 
-### Error Handling
 
-Custom data sources should include proper error handling:
-
-```tsx
-actions: {
-  get: async (entityId: string) => {
-    try {
-      const result = await yourDataSourceCall(entityId);
-      return result;
-    } catch (error) {
-      throw new Error(`Failed to fetch entity: ${error.message}`);
-    }
-  }
-}
-```
 
 ### Validation Requirements
 
@@ -3904,3 +3996,141 @@ export default function YourPage() {
 Slots provide a powerful way to enhance collection pages with custom functionality while maintaining the structure and features of the AutoPatterns system.
 
 ---
+
+# Error Handling for HTTP Requests
+
+**⚠️ CRITICAL**: When implementing custom data sources that make HTTP requests, you **MUST** wrap specific HTTP calls with proper error handling. This ensures consistent error management, prevents unhandled promise rejections, and provides better user experience.
+
+## What Requires Error Handling
+
+**ONLY the following HTTP requests** in your custom data source actions must be wrapped with `errorHandler`:
+
+- **httpClient from @wix/essentials** (e.g., `httpClient.request(getDummyEntity(...))`)
+- **Wix APIs** (e.g., `wix/data`, `wix/stores`, `items.get()`, `items.insert()`, `collections.getDataCollection()`)
+- **httpClient.fetchWithAuth()** calls
+
+**DO NOT use errorHandler with:**
+
+- **External API calls** using `fetch()`, `axios.get()`, or other HTTP libraries
+- **Custom HTTP clients** (e.g., any non-Wix HTTP request library)
+- **Third-party API calls** using non-Wix HTTP methods
+
+**EXCEPTION**: SDK actions that you get from the AutoPatterns SDK (e.g., `sdk.getOptimisticActions()`, `sdk.getSchema()`) do NOT need error handling as they are already handled internally.
+
+## Why Error Handling is Required
+
+Custom data sources often make HTTP requests to Wix APIs and services. Without proper error handling:
+
+- **Unhandled Promise Rejections**: HTTP failures can crash your application
+- **Poor User Experience**: Users don't get meaningful error messages
+- **Inconsistent Error Management**: Different parts of your app handle errors differently
+- **Debugging Difficulties**: Hard to trace and diagnose API failures
+
+## Using @wix/essentials errorHandler
+
+The recommended approach is to use the `errorHandler` from `@wix/essentials` package, which provides consistent error handling patterns across Wix applications.
+
+### Installation
+
+First, ensure `@wix/essentials` is installed in your project:
+
+```bash
+npm install @wix/essentials
+```
+
+### Basic Error Handling Pattern
+
+Wrap Wix HTTP requests in your custom data source actions with `errorHandler.withErrorHandler`:
+
+```typescript
+import { errorHandler } from '@wix/essentials';
+
+// In your custom data source actions
+actions: {
+  get: async (entityId: string) => {
+    return errorHandler.withErrorHandler(
+      async () => {
+        const response = await httpClient.request(
+          getDummyEntity({ dummyEntityId: entityId })
+        );
+        return response.data.dummyEntity;
+      },
+      {}
+    );
+  },
+}
+```
+
+### Examples of HTTP Requests That Need Error Handling
+
+**httpClient from @wix/essentials:**
+
+```typescript
+return errorHandler.withErrorHandler(async () => {
+  const response = await httpClient.request(
+    getDummyEntity({ dummyEntityId: entityId })
+  );
+  return response.data.dummyEntity;
+}, {});
+```
+
+**Wix APIs (wix/data, wix/stores):**
+
+```typescript
+return errorHandler.withErrorHandler(async () => {
+  return await items.get(collectionId, entityId);
+}, {});
+```
+
+**httpClient.fetchWithAuth() calls:**
+
+```typescript
+return errorHandler.withErrorHandler(async () => {
+  const response = await httpClient.fetchWithAuth("/api/data");
+  return await response.json();
+}, {});
+```
+
+### Examples of HTTP Requests That Do NOT Need Error Handling
+
+**External API calls (using fetch, axios, etc.):**
+
+```typescript
+// ✅ CORRECT - No error handling needed for external APIs
+const response = await fetch("https://api.example.com/data");
+return await response.json();
+
+// ✅ CORRECT - No error handling needed for axios
+const response = await axios.get("https://api.example.com/data");
+return response.data;
+```
+
+**Third-party HTTP libraries:**
+
+```typescript
+// ✅ CORRECT - No error handling needed for third-party HTTP clients
+const response = await someThirdPartyHttpClient.get("/data");
+return response.data;
+```
+
+## Integration with AutoPatterns Error Handling
+
+The error handling in your custom data source integrates seamlessly with AutoPatterns' built-in error handling:
+
+1. **User-Friendly Messages**: Errors are displayed to users in a consistent format
+2. **Retry Mechanisms**: Users can retry failed operations
+3. **Loading States**: Proper loading states during HTTP requests
+4. **Error Boundaries**: Errors are caught and handled gracefully
+
+## Validation Checklist
+
+Before deploying your custom data source, ensure:
+
+✅ **httpClient from @wix/essentials** is wrapped with `errorHandler.withErrorHandler`
+✅ **Wix APIs (wix/data, wix/stores, etc)** are wrapped with `errorHandler.withErrorHandler`
+✅ **httpClient.fetchWithAuth()** calls are wrapped with `errorHandler.withErrorHandler`
+✅ **External API calls are NOT wrapped** with errorHandler (e.g., fetch(), axios, third-party HTTP clients)
+✅ **SDK actions are used directly** without error handling (e.g., `sdk.getOptimisticActions()`, `sdk.getSchema()`)
+✅ **@wix/essentials** is installed as a dependency
+
+---

package/dist/docs/bulk_actions.md

@@ -174,11 +174,8 @@ Custom bulk actions execute JavaScript code that you define for bulk operations.
    - Be registered in the `actions` property of your `PatternsWizardOverridesProvider`
    - Follow JavaScript identifier naming rules (camelCase recommended)
 
-2. The implementation must return an object with:
-   - `label`: Text displayed for the action
-   - `icon`: An Icon component from "@wix/wix-ui-icons-common"
-   - `onClick`: Handler function for the bulk action
-   - `hidden` (optional): Boolean to hide the action when true
+2. The implementation must return a `ResolvedAction`:
+   For complete field documentation, see [ResolvedAction Reference](./resolved_action.md).
 
 3. The implementation must:
    - Use the correct type: `CustomBulkActionsActionResolver`

package/dist/docs/collection_page_actions.md

@@ -64,7 +64,7 @@ Custom collection page actions execute JavaScript code that you define for colle
    ```typescript
    import { CustomActionCollectionPageActionResolver } from '@wix/auto-patterns';
    import React from 'react';
-   import { Download } from '@wix/ui-icons-common';
+   import { Download } from '@wix/wix-ui-icons-common';
 
    // IMPORTANT: Function name MUST match the action id in your configuration
    export const exportCollection: CustomActionCollectionPageActionResolver = (params) => {
@@ -184,16 +184,7 @@ Row click actions are configured at the table level using the `onRowClick` prope
 
 ⚠️ **CRITICAL**: When you configure `onRowClick` in your TypeScript configuration, you MUST provide a complete working implementation. The Auto Patterns framework cannot function without it.
 
-Custom row click actions use the `CustomActionCollectionPageActionOnRowClickResolver` type and MUST return a `ResolvedAction` object with all required properties:
-
-#### Required Return Object Structure:
-```typescript
-return {
-  label: string,        // REQUIRED: Action label
-  icon: ReactElement,   // REQUIRED: Icon component
-  onClick: () => void   // REQUIRED: Click handler function
-};
-```
+Custom row click actions use the `CustomActionCollectionPageActionOnRowClickResolver` type and MUST return a `ResolvedAction`. See [ResolvedAction Reference](./resolved_action.md) for complete field documentation.
 
 #### Complete Implementation Example:
 
@@ -353,7 +344,7 @@ export const quickToggle: CustomActionCollectionPageActionOnRowClickResolver = (
 - **MANDATORY IMPLEMENTATION**: If you configure `onRowClick` in TypeScript configuration, you MUST provide a complete working implementation - the framework cannot function without it
 - The action `id` in the configuration MUST exactly match the function name exported from your actions folder
 - The implementation must use the `CustomActionCollectionPageActionOnRowClickResolver` type
-- **Required Return Object**: Must return an object with `label`, `icon`, and `onClick` properties - all are required
+- **Required Return Object**: Must return a `ResolvedAction` object - see [ResolvedAction Reference](./resolved_action.md)
 - Access the clicked item's data through `actionParams.item`
 - The implementation must be exported as a named export and registered in your `PatternsWizardOverridesProvider`
 - When `onRowClick` is configured, the default navigation to entity page is completely disabled

package/dist/docs/custom_overrides.md

@@ -4,6 +4,7 @@
 
 - **Custom overrides are restricted to the defined areas only** - attempting to override or modify any other aspect of `AutoPatternsApp` is prohibited and can cause unexpected behavior
 - **Always verify override implementation** - when implementing custom overrides, you MUST ensure they are correctly imported and passed to the `PatternsWizardOverridesProvider`
+- **CRITICAL: Error handling for custom actions** - Custom actions that make external API calls (using `fetch()`, `axios`, etc.) should NOT use `errorHandler.withErrorHandler`. Only Wix HTTP requests (httpClient from @wix/essentials, Wix APIs like wix/data and wix/stores, and httpClient.fetchWithAuth()) require errorHandler wrapping. See the "Error Handling for HTTP Requests" section for details.
 
 The `PatternsWizardOverridesProvider` allows you to inject custom code to override default behaviors or add additional functionality. Below are the areas where overrides can be applied:
 
@@ -810,22 +811,7 @@ When implementing custom data sources, you need to map your data source field ty
 - **Reference fields** → `'REFERENCE'`
 - **URL fields** → `'URL'`
 
-### Error Handling
 
-Custom data sources should include proper error handling:
-
-```tsx
-actions: {
-  get: async (entityId: string) => {
-    try {
-      const result = await yourDataSourceCall(entityId);
-      return result;
-    } catch (error) {
-      throw new Error(`Failed to fetch entity: ${error.message}`);
-    }
-  }
-}
-```
 
 ### Validation Requirements
 

package/dist/docs/entity_page_actions.md

@@ -55,7 +55,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 
   return {
     label: 'My More Action',
-    icon: <MyIcon />, // optional
+    icon: <MyIcon />, // required
     onClick: () => {
       // Your custom logic here
     },
@@ -75,7 +75,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 - The implementation must use the `CustomEntityPageActionResolver` type.
 - The implementation must be exported as a named export (not default export).
 - The function receives `{ actionParams, sdk }` as parameters.
-- The returned object must include at least a `label` and an `onClick` handler (optionally an `icon`).
+- The returned object must be a `ResolvedAction`. See [ResolvedAction Reference](./resolved_action.md) for complete documentation.
 
 ---
 
@@ -86,7 +86,7 @@ export const myMoreAction: CustomEntityPageActionResolver = (params) => {
 ✓ Custom actions match implementations in overrides
 ✓ The resolver is exported and registered in the `actions` property of your `PatternsWizardOverridesProvider`
 ✓ The function signature matches `CustomEntityPageActionResolver`
-✓ The returned object includes `label`, `onClick`, and optionally `icon`
+✓ The returned object is a `ResolvedAction` (see [ResolvedAction Reference](./resolved_action.md))
 
 ---
 

package/dist/docs/entity_page_view_actions.md

@@ -96,7 +96,7 @@ View mode actions follow the same resolver patterns as collection page actions:
 These actions are handled automatically by the AutoPatterns framework using the configuration provided.
 
 ### For Custom Actions
-Custom actions require resolver implementations:
+Custom actions require resolver implementations that return a `ResolvedAction` object. See [ResolvedAction Reference](./resolved_action.md) for complete field documentation.
 
 ```typescript
 import { CustomEntityPageActionResolver } from '@wix/auto-patterns/types';
@@ -107,7 +107,7 @@ export const duplicateProduct: CustomEntityPageActionResolver = (params) => {
   const schema = sdk.getSchema(sdk.collectionId);
   return {
     label: 'Duplicate Product',
-    icon: <DuplicateIcon />, // optional
+    icon: <DuplicateIcon />, // required
     onClick: async () => {
       // Your custom duplication logic here
       await schema.actions.create({