@wix/auto-patterns 1.23.0 → 1.25.0

package/dist/docs/entity_page.md

@@ -11,8 +11,72 @@ All entity pages must have:
 
 * Displays details for a **single entity**.
 * Always tied to a single Wix collection.
+* Supports **two distinct modes**: **view mode** and **edit mode** with separate page configurations.
 
-> The custom actions must be defined inside the `moreActions` array.
+## Entity Page Modes
+
+AutoPatterns supports two entity page modes that can be configured as separate pages:
+
+### Edit Mode (Default)
+- **Purpose**: Allows users to modify entity data
+- **UI**: Uses `@wix/patterns` `EntityPage` component with built-in Save/Cancel actions
+- **Actions**: Only supports `moreActions` (custom actions in the "more" menu)
+- **Default Mode**: When `mode` is not specified, defaults to edit mode
+
+### View Mode
+- **Purpose**: Displays entity data in read-only format with rich action capabilities
+- **Actions**: Supports `primaryActions`, `secondaryActions`, and `moreActions` (collection-style actions)
+- **Mode**: Must be explicitly set with `mode: 'view'`
+
+
+## Routing Patterns
+
+When implementing both view and edit modes for the same entity, use these routing patterns:
+
+- **View Mode**: `/entity/:entityId` (e.g., `/product/:productId`)
+- **Edit Mode**: `/entity/edit/:entityId` (e.g., `/product/edit/:productId`)
+
+This pattern allows:
+- Clear distinction between view and edit URLs
+- Natural navigation flow between modes
+
+## View Mode: Purpose and API
+
+### Purpose of View Mode
+View mode is primarily intended for **read-only entity presentation** with rich action capabilities by default; however, it also supports interactive or editable custom components if needed:
+
+- **Data Display**: Present entity information in a clean, read-only format
+- **Action Hub**: Provide primary, secondary, and more actions for entity operations
+- **Navigation Center**: Enable seamless transitions to edit mode and other workflows
+- **Rich Content**: Display images, rich text, and complex data types optimally
+
+
+See [Entity Page View Actions](./entity_page_view_actions.md) for detailed action configuration.
+
+#### Out-of-the-Box Features
+
+**Automatic Edit Navigation**: When a corresponding edit mode page exists, view mode automatically adds an "Edit [EntityName]" action to the more actions menu.
+
+**Back Navigation**: Automatic "Back" button that navigates to the parent collection page.
+
+## Action Configuration
+
+Entity page action configuration depends on the mode:
+
+- **Edit Mode**: Supports only `moreActions`. See [Entity Page Actions](./entity_page_actions.md)
+- **View Mode**: Supports full action API (`primaryActions`, `secondaryActions`, `moreActions`). See [Entity Page View Actions](./entity_page_view_actions.md)
+
+### Edit Mode Actions
+- **Supported**: `moreActions` only
+- **Built-in**: Save and Cancel actions are automatically provided
+- **Custom Actions**: Must be defined in the `moreActions` array
+
+### View Mode Actions
+- **Supported**: `primaryActions`, `secondaryActions`, and `moreActions`
+- **Pattern**: Follows collection page action patterns
+- **Flexibility**: Full control over all action areas
+
+> The custom actions must be defined inside the `moreActions` array for edit mode, but view mode supports actions in all areas.
 
 > Note: You do not need to define a custom action to navigate to the entity page. This behavior is built-in — clicking on a row in the collection table automatically navigates to the corresponding entity page.
 

package/dist/docs/entity_page_actions.md

@@ -1,8 +1,10 @@
-## Entity Page Actions: `moreActions` Support
+## Entity Page Edit Mode Actions: `moreActions` Support
 
-Entity pages in AutoPatternsApp support not only a primary action (such as "Save" or "Delete") but also a flexible set of **more actions** (sometimes called "secondary actions" or `moreActions`). These allow you to provide additional contextual actions for the entity, such as custom logic, or grouped actions.
+Entity pages in **edit mode** support not only built-in actions (such as "Save" and "Cancel") but also a flexible set of **more actions** (sometimes called "secondary actions" or `moreActions`). These allow you to provide additional contextual actions for the entity, such as custom logic, or grouped actions.
 
-> **Note:** All custom actions for entity pages must be placed in the `moreActions` array. Do not place custom actions as primary actions on entity pages. The `moreActions` array is the only supported location for custom actions on entity pages.
+> **Note:** This documentation covers **edit mode** entity pages only. Edit mode supports only `moreActions`. For **view mode** entity pages that support `primaryActions`, `secondaryActions`, and `moreActions`, see [Entity Page View Actions](./entity_page_view_actions.md).
+
+> **Edit Mode Limitation:** All custom actions for edit mode entity pages must be placed in the `moreActions` array. Do not place custom actions as primary actions on edit mode entity pages. The `moreActions` array is the only supported location for custom actions on edit mode entity pages.
 
 ### Configuration Structure
 
@@ -39,16 +41,16 @@ Entity pages in AutoPatternsApp support not only a primary action (such as "Save
 
 ---
 
-### CustomEntityPageMoreActionsActionResolver
+### CustomEntityPageActionResolver
 
-The `CustomEntityPageMoreActionsActionResolver` type is used to implement custom actions for the `moreActions` menu on entity pages in AutoPatternsApp. Each action in the `moreActions` array must have a corresponding resolver function registered in your overrides.
+The `CustomEntityPageActionResolver` type is used to implement custom actions for the `moreActions` menu on entity pages in AutoPatternsApp. Each action in the `moreActions` array must have a corresponding resolver function registered in your overrides.
 
 #### Function Signature
 
 ```typescript
-import { CustomEntityPageMoreActionsActionResolver } from '@wix/auto-patterns/types';
+import { CustomEntityPageActionResolver } from '@wix/auto-patterns/types';
 
-export const myMoreAction: CustomEntityPageMoreActionsActionResolver = (params) => {
+export const myMoreAction: CustomEntityPageActionResolver = (params) => {
   const { actionParams: { entity, form } , sdk } = params;
 
   return {
@@ -67,10 +69,10 @@ export const myMoreAction: CustomEntityPageMoreActionsActionResolver = (params)
 
 ---
 
-#### Key Points for CustomEntityPageMoreActionsActionResolver
+#### Key Points for CustomEntityPageActionResolver
 
 - The action `id` in the configuration MUST exactly match the function name exported from your actions folder.
-- The implementation must use the `CustomEntityPageMoreActionsActionResolver` type.
+- 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`).
@@ -83,10 +85,10 @@ export const myMoreAction: CustomEntityPageMoreActionsActionResolver = (params)
 ✓ Each action type only includes its required field(s)
 ✓ Custom actions match implementations in overrides
 ✓ The resolver is exported and registered in the `actions` property of your `PatternsWizardOverridesProvider`
-✓ The function signature matches `CustomEntityPageMoreActionsActionResolver`
+✓ The function signature matches `CustomEntityPageActionResolver`
 ✓ The returned object includes `label`, `onClick`, and optionally `icon`
 
 ---
 
 **Summary:**
-The `CustomEntityPageMoreActionsActionResolver` enables you to add custom, contextual actions to the "More Actions" menu on your entity pages. Implement the resolver, export it, and reference it by `id` in your config for seamless integration.
+The `CustomEntityPageActionResolver` enables you to add custom, contextual actions to the "More Actions" menu on your entity pages. Implement the resolver, export it, and reference it by `id` in your config for seamless integration.

package/dist/docs/entity_page_view_actions.md

@@ -0,0 +1,137 @@
+# Entity Page View Mode Actions
+
+View mode supports the complete collection-style actions API, providing maximum flexibility for entity operations.
+
+## Supported Action Types
+
+### Primary Actions
+The main call-to-action, typically for the most common operation:
+
+```typescript
+primaryActions: {
+  type: 'action',
+  action: {
+    item: {
+      id: 'createEntity',
+      label: 'Create New',
+      type: 'create',
+      create: {
+        mode: 'page',
+        page: { id: 'EntityEditPageId' }
+      }
+    }
+  }
+}
+```
+
+### Secondary Actions
+Supporting actions displayed alongside primary actions:
+
+```typescript
+secondaryActions: {
+  type: 'action',
+  action: {
+    item: {
+      id: 'duplicateEntity',
+      label: 'Duplicate',
+      type: 'custom',
+    }
+  }
+}
+```
+
+### More Actions
+Additional contextual actions in dropdown menu:
+
+```typescript
+moreActions: [
+  {
+    id: 'shareEntity',
+    type: 'custom',
+    label: 'Share',
+  }
+]
+```
+
+## Action Menu Support
+
+View mode also supports menu-style actions for grouping related operations:
+
+```typescript
+primaryActions: {
+  type: 'menu',
+  menu: {
+    label: 'Actions',
+    items: [
+      {
+        id: 'duplicateProduct',
+        label: 'Duplicate',
+        type: 'custom',
+      },
+      { type: 'divider' },
+      {
+        id: 'shareProduct',
+        type: 'custom',
+        label: 'Share'
+      }
+    ]
+  }
+}
+```
+
+## Automatic Edit Action
+
+View mode automatically provides an "Edit [EntityName]" action in the more actions menu when:
+- An edit mode page exists for the same collection
+- The edit page has no explicit mode or `mode: 'edit'`
+- The view page has `mode: 'view'`
+
+This action is automatically added and doesn't need to be configured manually.
+
+## Action Resolvers
+
+View mode actions follow the same resolver patterns as collection page actions:
+
+### For Standard Actions (create)
+These actions are handled automatically by the AutoPatterns framework using the configuration provided.
+
+### For Custom Actions
+Custom actions require resolver implementations:
+
+```typescript
+import { CustomEntityPageActionResolver } from '@wix/auto-patterns/types';
+
+export const duplicateProduct: CustomEntityPageActionResolver = (params) => {
+  const { actionParams: { entity }, sdk } = params;
+
+  const schema = sdk.getSchema(sdk.collectionId);
+  return {
+    label: 'Duplicate Product',
+    icon: <DuplicateIcon />, // optional
+    onClick: async () => {
+      // Your custom duplication logic here
+      await schema.actions.create({
+        ...entity,
+        name: `${entity.name} (Copy)`
+      });
+    },
+  };
+};
+```
+
+## Best Practices
+
+### When to Use Each Action Type
+
+**Primary Actions**: Use for the most common user action (typically "Create" or main workflow action)
+
+**Secondary Actions**: Use for supporting workflows like "Duplicate"
+
+**More Actions**: Use for:
+- Less common operations
+- Administrative functions
+- Actions that need confirmation
+
+### Navigation Patterns
+
+1. **View → Create**: Use primary actions with `type: 'create'`

package/dist/docs/index.md

@@ -43,8 +43,12 @@ This index maps user requests to the appropriate section IDs for fetching releva
 **Keywords**: entity page layout, detail page configuration, field arrangement, layout structure, grid system, column spans, main/sidebar sections, field grouping, container usage, custom components, 12-column grid
 
 ### ID: `entity_page_actions`
-**Topics**: Entity page actions, moreActions, custom entity actions
-**Keywords**: entity page actions, detail page operations, moreActions, secondary actions, custom entity actions, entity-specific operations, action menus
+**Topics**: Entity page edit mode actions, moreActions, custom entity actions
+**Keywords**: entity page actions, edit mode actions, moreActions, custom entity actions, entity-specific operations, action menus
+
+### ID: `entity_page_view_actions`
+**Topics**: Entity page view mode actions, primaryActions, secondaryActions, collection-style actions
+**Keywords**: view mode actions, primaryActions, secondaryActions, read-only entity actions, entity page view operations, collection-style entity actions, navigation actions
 
 ### ID: `installation`
 **Topics**: Package installation, setup process, component integration, provider setup

package/dist/docs/pages_configuration.md

@@ -5,7 +5,6 @@
 - **Pages array must contain exactly two pages** - one collectionPage and one entityPage
 - **Exactly one page must have `appMainPage: true`** to designate it as the main page
 - **All page IDs referenced in relationships must exist in the configuration** - validate all `parentPageId` and `entityPageId` references
-- **Bind `type` strictly to matching fields** - if `type: 'collectionPage'`, only `collectionPage` field exists (no `entityPage` field), and vice versa
 
 ## Default Generation
 
@@ -18,12 +17,6 @@
     * The route path **must** include a descriptive segment (e.g., `/product/:entityId`, `/pet/:entityId`)
     * **Never use just `/:entityId`** - this conflicts with the collection page route and breaks routing
 
-## Type and Structure Binding
-
-* If `type: 'collectionPage'`, then **only** `collectionPage` field exists (no `entityPage` field).
-* If `type: 'entityPage'`, then **only** `entityPage` field exists (no `collectionPage` field).
-* **No cross-mixing** allowed.
-
 ## Page Connection Configuration
 
 ### Main Page Designation
@@ -88,11 +81,8 @@ A two-way connection must be established between collection pages and entity pag
 * **Route Structure**: Entity pages must use `/[segment]/:entityId` format (e.g., `/product/:entityId` or `/pets/:entityId`), never just `/:entityId`
 * **Route Parameters Configuration**: All entity pages must have both a dynamic parameter in `route.path` and a matching configuration in `route.params`
 
-## ⚠️ Common Type and Route Mistakes to Avoid
+## ⚠️ Common Route and Configuration Mistakes to Avoid
 
-- Using incorrect field types
-- Missing required fields
-- Including fields from wrong page type
 - Missing route.params for entity pages
 - Using `/:entityId` instead of `/segment/:entityId` for entity page routes (causes routing conflicts)
 

package/dist/docs/sdk_utilities.md

@@ -48,9 +48,15 @@ const optimisticActions = sdk.getOptimisticActions(sdk.collectionId);
 const schema = sdk.getSchema(sdk.collectionId);
 
 optimisticActions.operation(items, {
-  submit: async (items) => schema.actions.serverMethod(items),
+  submit: async (items) => {
+    // Handle potential undefined schema
+    if (schema) {
+      return await schema.actions.serverMethod(items);
+    }
+    return items; // fallback when schema is unavailable
+  },
   successToast: 'Success message',
-  errorToast: (err, {retry}) => ({ text: 'Error message', action: { text: 'Retry', onClick: retry }})
+  errorToast: (err, {retry}) => ({ message: 'Error message', action: { text: 'Retry', onClick: retry }})
 });
 ```
 
@@ -81,7 +87,7 @@ interface OptimisticParams<T> {
 }
 
 interface ToastConfig {
-  text: string;
+  message: string; // Note: Use 'message' property, not 'text'
   action?: { text: string; onClick: () => void };
 }
 ```
@@ -90,8 +96,9 @@ interface ToastConfig {
 
 **Before using optimistic actions:**
 - Verify `sdk.getOptimisticActions(collectionId)` returns valid instance
-- Verify `sdk.getSchema(collectionId)` returns valid schema
+- **Always check for undefined schema**: `sdk.getSchema(collectionId)` can return `undefined` - handle this case in your submit functions
 - For delete operations: `showUndoToast: true` is mandatory
 - All `submit` functions must return a Promise
+- **Toast property**: Use `message` property in ToastConfig, not `text`
 
 **SDK Parameter:** Available in custom actions and modals. See SDK Utilities section for complete interface.

package/dist/docs/wix_fqdn_custom_data_source.md

@@ -1,26 +1,41 @@
 # FQDN-Based Custom Data Source Implementation
 
+**🛑 CRITICAL PREREQUISITE**: This guide explains a specialized feature that exists within the broader auto-patterns framework. You **CANNOT** implement this guide without first having the complete content of the WixAutoPatternsGuide.
+
+**📋 MANDATORY FIRST STEP**: Before proceeding with this FQDN-specific implementation:
+1. **You MUST call the `WixAutoPatternsGuide` tool first** to get the foundational auto-patterns knowledge
+2. **This document is NOT standalone** - it's an advanced feature guide that builds upon the core auto-patterns concepts
+3. **Without the WixAutoPatternsGuide content**, you will not understand the basic concepts, component structure, or implementation patterns required for this FQDN implementation
+
 When implementing a custom data source based on a Wix Business API FQDN, you'll need to understand several key concepts and follow specific implementation patterns. This guide covers the complete process from schema extraction to creating a foundation structure that **you will need to complete**.
 
 **⚠️ IMPORTANT**: This guide creates a foundation with helpful comments and unimplemented actions that throw exceptions. The actual data source implementation (CRUD operations) must be completed by you using the appropriate Wix Business API client library.
 
 **📝 MINIMAL IMPLEMENTATION APPROACH**: This guide focuses on creating a basic, functional dashboard page. Custom overrides (actions, columns, components, etc.) should only be implemented when explicitly requested by the user. A simple dashboard page requires only the core custom data source implementation without any additional overrides.
 
-## Prerequisites: Required Tools
+## Prerequisites: Required Tools and Knowledge
+
+**🛑 ABSOLUTE REQUIREMENT - WixAutoPatternsGuide Content**:
+- **You MUST have the complete WixAutoPatternsGuide content** before starting this implementation
+- **This FQDN guide is NOT self-contained** - it's a specialized extension of the main auto-patterns guide
+- **If you haven't called the `WixAutoPatternsGuide` tool yet**, stop now and call it first
+- **This guide will reference concepts, components, and patterns** that are only explained in the main guide
 
 **🛑 CRITICAL**: Before proceeding with this guide, you must have the following tools available:
-- `WixPatternsGuide` tool for understanding auto-patterns fundamentals and implementation patterns
+- `WixAutoPatternsGuide` tool for understanding auto-patterns fundamentals and implementation patterns (**MANDATORY FIRST STEP**)
 - `fqdn_schema` tool for extracting schema information from FQDNs
 - `client_lib` tool for determining the correct client library package
 
 **If these tools are not available, you CANNOT continue with this guide.**
 
 **Auto-Patterns Context Requirement:**
-If you haven't already used the `WixPatternsGuide` tool in this conversation, you MUST call it first to understand:
+If you haven't already used the `WixAutoPatternsGuide` tool in this conversation, you MUST call it first to understand:
 - How AutoPatternsApp works
 - AppConfig structure and requirements
 - Custom data source implementation patterns
 - Best practices for auto-patterns development
+- Basic component structure and routing
+- Provider setup and configuration
 
 **Without this foundational knowledge, you cannot successfully implement FQDN-based custom data sources.**
 
@@ -65,7 +80,10 @@ This will tell you which library to import for your custom data source implement
 
 Transform the FQDN schema from Step 1 into a AutoPatterns-compatible SchemaConfig by mapping the FQDN field types to AutoPatterns field types. Identify appropriate fields for `displayField` and `idField` based on your FQDN schema.
 
-**Note**: When implementing a custom data source, you can leave `supportedQueryOperators` empty (`supportedQueryOperators: []`) even if you know the supported operators. This is because the custom data source will handle all query operations directly through your implementation.
+**🛑 MANDATORY - Query Operators Must Be Empty Array**: When implementing a custom data source, you **MUST** set `supportedQueryOperators: []` (empty array) for all fields. This is required because:
+- Custom data sources handle all query operations directly through your implementation
+- You don't need to specify individual operators for each field
+- The custom data source `find` action will receive all queries regardless of declared operators
 
 ### ⚠️ CRITICAL: Field ID Conversion from snake_case to camelCase
 
@@ -112,7 +130,7 @@ export const myCustomDataSource = async (collectionId: string, context: any) =>
       // Field definitions based on your FQDN schema mapping
     },
     displayField: 'name',
-    idField: '_id',
+    idField: 'id',
     actions: {
       get: async (entityId: string) => {
         // TODO: Implement using your FQDN client library
@@ -218,6 +236,7 @@ If the user specifically requests custom actions for your FQDN-based data source
 ✅ **Schema Extraction**: Used fqdn_schema tool to understand entity structure
 ✅ **Client Library**: Used client_lib tool to identify correct SDK package
 ✅ **Field Mapping**: Mapped FQDN field types to AutoPatterns field types
+✅ **🛑 MANDATORY: Empty Query Operators**: Set `supportedQueryOperators: []` for ALL fields to avoid TypeScript errors
 ✅ **⚠️ CRITICAL: Field ID Conversion**: Converted individual field segments from snake_case to camelCase while preserving field path structure in SchemaConfig and AppConfig
 ✅ **AppConfig Update**: Set `entityTypeSource: "custom"` and provided custom.id
 ✅ **Custom Data Source Structure**: Followed "Custom Overrides" section for folder structure and registration
@@ -235,6 +254,7 @@ If the user specifically requests custom actions for your FQDN-based data source
 - **⚠️ CRITICAL: Implementing Unnecessary Overrides**: Do NOT implement custom actions, column overrides, or custom components unless explicitly requested by the user - a basic dashboard page only needs the core custom data source
 - **⚠️ CRITICAL: Inconsistent Field ID Casing**: Failing to convert individual field segments from snake_case to camelCase while preserving field path structure in SchemaConfig and AppConfig - this is the most common mistake and will cause field mapping failures
 - **⚠️ CRITICAL: Implementing Actions**: DO NOT implement the schema actions - they should contain helpful comments and throw unimplemented exceptions for the user to complete
+- **🛑 CRITICAL: Query Operators MUST Be Empty Array**: You **MUST** use `supportedQueryOperators: []` (empty array) for all fields - attempting to specify actual operators will cause TypeScript compilation errors and is not supported for custom data sources
 - **Mismatched Field Types**: Ensure FQDN field types are correctly mapped to AutoPatterns types
 - **Wrong Client Library**: Use the exact client library returned by the client_lib tool
 - **ID Field Confusion**: Ensure the idField matches what your FQDN API actually uses (often `_id` for Wix APIs)

package/dist/esm/components/AutoPatternsCollectionComponent/AutoPatternsCollectionComponent.js

@@ -14,14 +14,15 @@ export const AutoPatternsCollectionComponent = _ref => {
     ...sharedConfig
   } = component;
   const memoized = useMemo(() => {
-    if (!layout?.length) {
+    var _layout$find, _layout$find2;
+    if (!(layout != null && layout.length)) {
       return {
         componentToRender: null,
         componentType: 'Table'
       };
     }
-    const tableConfig = layout.find(item => item.type === 'Table')?.table;
-    const gridConfig = layout.find(item => item.type === 'Grid')?.grid;
+    const tableConfig = (_layout$find = layout.find(item => item.type === 'Table')) == null ? void 0 : _layout$find.table;
+    const gridConfig = (_layout$find2 = layout.find(item => item.type === 'Grid')) == null ? void 0 : _layout$find2.grid;
     let componentType = 'Table';
     let componentToRender = null;
     if (tableConfig && gridConfig) {

package/dist/esm/components/AutoPatternsCollectionComponent/AutoPatternsCollectionComponent.js.map

@@ -1 +1 @@
-{"version":3,"names":["AutoPatternsTableGridSwitch","AutoPatternsTable","AutoPatternsGrid","SchemaProvider","SkeletonCollection","React","useMemo","AutoPatternsCollectionComponent","_ref","component","index","layout","sharedConfig","memoized","length","componentToRender","componentType","tableConfig","find","item","type","table","gridConfig","grid","config","createElement","configuration","Fragment","key","collection","collectionId","skeleton"],"sources":["../../../../src/components/AutoPatternsCollectionComponent/AutoPatternsCollectionComponent.tsx"],"sourcesContent":["import { CollectionComponentConfig } from '../../types';\nimport { AutoPatternsTableGridSwitch } from '../AutoPatternsTableGridSwitch/AutoPatternsTableGridSwitch';\nimport { AutoPatternsTable } from '../AutoPatternsTable';\nimport { AutoPatternsGrid } from '../AutoPatternsGrid';\nimport { SchemaProvider } from '../../providers';\nimport { SkeletonCollection } from '../AutoPatternsCollectionPageContent/SkeletonCollection';\nimport React, { useMemo } from 'react';\n\nexport const AutoPatternsCollectionComponent = ({\n  component,\n  index,\n}: {\n  component: CollectionComponentConfig;\n  index: number;\n}) => {\n  const { layout, ...sharedConfig } = component;\n\n  const memoized = useMemo(() => {\n    if (!layout?.length) {\n      return {\n        componentToRender: null,\n        componentType: 'Table' as 'Table' | 'Grid',\n      };\n    }\n\n    const tableConfig = layout.find((item) => item.type === 'Table')?.table;\n    const gridConfig = layout.find((item) => item.type === 'Grid')?.grid;\n\n    let componentType: 'Table' | 'Grid' = 'Table';\n    let componentToRender: React.ReactNode = null;\n\n    if (tableConfig && gridConfig) {\n      const config = {\n        ...sharedConfig,\n        ...tableConfig,\n        ...gridConfig,\n      };\n      componentToRender = (\n        <AutoPatternsTableGridSwitch configuration={config} />\n      );\n    } else if (tableConfig) {\n      const config = { ...sharedConfig, ...tableConfig };\n      componentToRender = <AutoPatternsTable configuration={config} />;\n    } else if (gridConfig) {\n      componentType = 'Grid';\n      const config = { ...sharedConfig, ...gridConfig };\n      componentToRender = <AutoPatternsGrid configuration={config} />;\n    }\n\n    return { componentToRender, componentType };\n  }, [layout, sharedConfig]);\n\n  const { componentToRender, componentType } = memoized;\n\n  return (\n    <>\n      {componentToRender ? (\n        <SchemaProvider\n          key={`${sharedConfig.collection.collectionId}-${index}`}\n          collection={sharedConfig.collection}\n          skeleton={<SkeletonCollection componentType={componentType} />}\n        >\n          {componentToRender}\n        </SchemaProvider>\n      ) : null}\n    </>\n  );\n};\n"],"mappings":"AACA,SAASA,2BAA2B,QAAQ,4DAA4D;AACxG,SAASC,iBAAiB,QAAQ,sBAAsB;AACxD,SAASC,gBAAgB,QAAQ,qBAAqB;AACtD,SAASC,cAAc,QAAQ,iBAAiB;AAChD,SAASC,kBAAkB,QAAQ,yDAAyD;AAC5F,OAAOC,KAAK,IAAIC,OAAO,QAAQ,OAAO;AAEtC,OAAO,MAAMC,+BAA+B,GAAGC,IAAA,IAMzC;EAAA,IAN0C;IAC9CC,SAAS;IACTC;EAIF,CAAC,GAAAF,IAAA;EACC,MAAM;IAAEG,MAAM;IAAE,GAAGC;EAAa,CAAC,GAAGH,SAAS;EAE7C,MAAMI,QAAQ,GAAGP,OAAO,CAAC,MAAM;IAC7B,IAAI,CAACK,MAAM,EAAEG,MAAM,EAAE;MACnB,OAAO;QACLC,iBAAiB,EAAE,IAAI;QACvBC,aAAa,EAAE;MACjB,CAAC;IACH;IAEA,MAAMC,WAAW,GAAGN,MAAM,CAACO,IAAI,CAAEC,IAAI,IAAKA,IAAI,CAACC,IAAI,KAAK,OAAO,CAAC,EAAEC,KAAK;IACvE,MAAMC,UAAU,GAAGX,MAAM,CAACO,IAAI,CAAEC,IAAI,IAAKA,IAAI,CAACC,IAAI,KAAK,MAAM,CAAC,EAAEG,IAAI;IAEpE,IAAIP,aAA+B,GAAG,OAAO;IAC7C,IAAID,iBAAkC,GAAG,IAAI;IAE7C,IAAIE,WAAW,IAAIK,UAAU,EAAE;MAC7B,MAAME,MAAM,GAAG;QACb,GAAGZ,YAAY;QACf,GAAGK,WAAW;QACd,GAAGK;MACL,CAAC;MACDP,iBAAiB,gBACfV,KAAA,CAAAoB,aAAA,CAACzB,2BAA2B;QAAC0B,aAAa,EAAEF;MAAO,CAAE,CACtD;IACH,CAAC,MAAM,IAAIP,WAAW,EAAE;MACtB,MAAMO,MAAM,GAAG;QAAE,GAAGZ,YAAY;QAAE,GAAGK;MAAY,CAAC;MAClDF,iBAAiB,gBAAGV,KAAA,CAAAoB,aAAA,CAACxB,iBAAiB;QAACyB,aAAa,EAAEF;MAAO,CAAE,CAAC;IAClE,CAAC,MAAM,IAAIF,UAAU,EAAE;MACrBN,aAAa,GAAG,MAAM;MACtB,MAAMQ,MAAM,GAAG;QAAE,GAAGZ,YAAY;QAAE,GAAGU;MAAW,CAAC;MACjDP,iBAAiB,gBAAGV,KAAA,CAAAoB,aAAA,CAACvB,gBAAgB;QAACwB,aAAa,EAAEF;MAAO,CAAE,CAAC;IACjE;IAEA,OAAO;MAAET,iBAAiB;MAAEC;IAAc,CAAC;EAC7C,CAAC,EAAE,CAACL,MAAM,EAAEC,YAAY,CAAC,CAAC;EAE1B,MAAM;IAAEG,iBAAiB;IAAEC;EAAc,CAAC,GAAGH,QAAQ;EAErD,oBACER,KAAA,CAAAoB,aAAA,CAAApB,KAAA,CAAAsB,QAAA,QACGZ,iBAAiB,gBAChBV,KAAA,CAAAoB,aAAA,CAACtB,cAAc;IACbyB,GAAG,EAAE,GAAGhB,YAAY,CAACiB,UAAU,CAACC,YAAY,IAAIpB,KAAK,EAAG;IACxDmB,UAAU,EAAEjB,YAAY,CAACiB,UAAW;IACpCE,QAAQ,eAAE1B,KAAA,CAAAoB,aAAA,CAACrB,kBAAkB;MAACY,aAAa,EAAEA;IAAc,CAAE;EAAE,GAE9DD,iBACa,CAAC,GACf,IACJ,CAAC;AAEP,CAAC","ignoreList":[]}
+{"version":3,"names":["AutoPatternsTableGridSwitch","AutoPatternsTable","AutoPatternsGrid","SchemaProvider","SkeletonCollection","React","useMemo","AutoPatternsCollectionComponent","_ref","component","index","layout","sharedConfig","memoized","_layout$find","_layout$find2","length","componentToRender","componentType","tableConfig","find","item","type","table","gridConfig","grid","config","createElement","configuration","Fragment","key","collection","collectionId","skeleton"],"sources":["../../../../src/components/AutoPatternsCollectionComponent/AutoPatternsCollectionComponent.tsx"],"sourcesContent":["import { CollectionComponentConfig } from '../../types';\nimport { AutoPatternsTableGridSwitch } from '../AutoPatternsTableGridSwitch/AutoPatternsTableGridSwitch';\nimport { AutoPatternsTable } from '../AutoPatternsTable';\nimport { AutoPatternsGrid } from '../AutoPatternsGrid';\nimport { SchemaProvider } from '../../providers';\nimport { SkeletonCollection } from '../AutoPatternsCollectionPageContent/SkeletonCollection';\nimport React, { useMemo } from 'react';\n\nexport const AutoPatternsCollectionComponent = ({\n  component,\n  index,\n}: {\n  component: CollectionComponentConfig;\n  index: number;\n}) => {\n  const { layout, ...sharedConfig } = component;\n\n  const memoized = useMemo(() => {\n    if (!layout?.length) {\n      return {\n        componentToRender: null,\n        componentType: 'Table' as 'Table' | 'Grid',\n      };\n    }\n\n    const tableConfig = layout.find((item) => item.type === 'Table')?.table;\n    const gridConfig = layout.find((item) => item.type === 'Grid')?.grid;\n\n    let componentType: 'Table' | 'Grid' = 'Table';\n    let componentToRender: React.ReactNode = null;\n\n    if (tableConfig && gridConfig) {\n      const config = {\n        ...sharedConfig,\n        ...tableConfig,\n        ...gridConfig,\n      };\n      componentToRender = (\n        <AutoPatternsTableGridSwitch configuration={config} />\n      );\n    } else if (tableConfig) {\n      const config = { ...sharedConfig, ...tableConfig };\n      componentToRender = <AutoPatternsTable configuration={config} />;\n    } else if (gridConfig) {\n      componentType = 'Grid';\n      const config = { ...sharedConfig, ...gridConfig };\n      componentToRender = <AutoPatternsGrid configuration={config} />;\n    }\n\n    return { componentToRender, componentType };\n  }, [layout, sharedConfig]);\n\n  const { componentToRender, componentType } = memoized;\n\n  return (\n    <>\n      {componentToRender ? (\n        <SchemaProvider\n          key={`${sharedConfig.collection.collectionId}-${index}`}\n          collection={sharedConfig.collection}\n          skeleton={<SkeletonCollection componentType={componentType} />}\n        >\n          {componentToRender}\n        </SchemaProvider>\n      ) : null}\n    </>\n  );\n};\n"],"mappings":"AACA,SAASA,2BAA2B,QAAQ,4DAA4D;AACxG,SAASC,iBAAiB,QAAQ,sBAAsB;AACxD,SAASC,gBAAgB,QAAQ,qBAAqB;AACtD,SAASC,cAAc,QAAQ,iBAAiB;AAChD,SAASC,kBAAkB,QAAQ,yDAAyD;AAC5F,OAAOC,KAAK,IAAIC,OAAO,QAAQ,OAAO;AAEtC,OAAO,MAAMC,+BAA+B,GAAGC,IAAA,IAMzC;EAAA,IAN0C;IAC9CC,SAAS;IACTC;EAIF,CAAC,GAAAF,IAAA;EACC,MAAM;IAAEG,MAAM;IAAE,GAAGC;EAAa,CAAC,GAAGH,SAAS;EAE7C,MAAMI,QAAQ,GAAGP,OAAO,CAAC,MAAM;IAAA,IAAAQ,YAAA,EAAAC,aAAA;IAC7B,IAAI,EAACJ,MAAM,YAANA,MAAM,CAAEK,MAAM,GAAE;MACnB,OAAO;QACLC,iBAAiB,EAAE,IAAI;QACvBC,aAAa,EAAE;MACjB,CAAC;IACH;IAEA,MAAMC,WAAW,IAAAL,YAAA,GAAGH,MAAM,CAACS,IAAI,CAAEC,IAAI,IAAKA,IAAI,CAACC,IAAI,KAAK,OAAO,CAAC,qBAA5CR,YAAA,CAA8CS,KAAK;IACvE,MAAMC,UAAU,IAAAT,aAAA,GAAGJ,MAAM,CAACS,IAAI,CAAEC,IAAI,IAAKA,IAAI,CAACC,IAAI,KAAK,MAAM,CAAC,qBAA3CP,aAAA,CAA6CU,IAAI;IAEpE,IAAIP,aAA+B,GAAG,OAAO;IAC7C,IAAID,iBAAkC,GAAG,IAAI;IAE7C,IAAIE,WAAW,IAAIK,UAAU,EAAE;MAC7B,MAAME,MAAM,GAAG;QACb,GAAGd,YAAY;QACf,GAAGO,WAAW;QACd,GAAGK;MACL,CAAC;MACDP,iBAAiB,gBACfZ,KAAA,CAAAsB,aAAA,CAAC3B,2BAA2B;QAAC4B,aAAa,EAAEF;MAAO,CAAE,CACtD;IACH,CAAC,MAAM,IAAIP,WAAW,EAAE;MACtB,MAAMO,MAAM,GAAG;QAAE,GAAGd,YAAY;QAAE,GAAGO;MAAY,CAAC;MAClDF,iBAAiB,gBAAGZ,KAAA,CAAAsB,aAAA,CAAC1B,iBAAiB;QAAC2B,aAAa,EAAEF;MAAO,CAAE,CAAC;IAClE,CAAC,MAAM,IAAIF,UAAU,EAAE;MACrBN,aAAa,GAAG,MAAM;MACtB,MAAMQ,MAAM,GAAG;QAAE,GAAGd,YAAY;QAAE,GAAGY;MAAW,CAAC;MACjDP,iBAAiB,gBAAGZ,KAAA,CAAAsB,aAAA,CAACzB,gBAAgB;QAAC0B,aAAa,EAAEF;MAAO,CAAE,CAAC;IACjE;IAEA,OAAO;MAAET,iBAAiB;MAAEC;IAAc,CAAC;EAC7C,CAAC,EAAE,CAACP,MAAM,EAAEC,YAAY,CAAC,CAAC;EAE1B,MAAM;IAAEK,iBAAiB;IAAEC;EAAc,CAAC,GAAGL,QAAQ;EAErD,oBACER,KAAA,CAAAsB,aAAA,CAAAtB,KAAA,CAAAwB,QAAA,QACGZ,iBAAiB,gBAChBZ,KAAA,CAAAsB,aAAA,CAACxB,cAAc;IACb2B,GAAG,EAAE,GAAGlB,YAAY,CAACmB,UAAU,CAACC,YAAY,IAAItB,KAAK,EAAG;IACxDqB,UAAU,EAAEnB,YAAY,CAACmB,UAAW;IACpCE,QAAQ,eAAE5B,KAAA,CAAAsB,aAAA,CAACvB,kBAAkB;MAACc,aAAa,EAAEA;IAAc,CAAE;EAAE,GAE9DD,iBACa,CAAC,GACf,IACJ,CAAC;AAEP,CAAC","ignoreList":[]}

package/dist/esm/components/AutoPatternsCollectionPageContent/AutoPatternsCollectionPageContent.js

@@ -17,7 +17,8 @@ export const AutoPatternsCollectionPageContent = _ref => {
         index: index
       });
     } else if (component.type === 'custom') {
-      const CustomComponent = overrides?.slots?.[component.id];
+      var _overrides$slots;
+      const CustomComponent = overrides == null || (_overrides$slots = overrides.slots) == null ? void 0 : _overrides$slots[component.id];
       if (!CustomComponent) {
         return null;
       }

package/dist/esm/components/AutoPatternsCollectionPageContent/AutoPatternsCollectionPageContent.js.map

@@ -1 +1 @@
-{"version":3,"names":["React","usePatternsWizardOverridesContext","AutoPatternsCollectionComponent","AutoPatternsCollectionPageContent","_ref","configuration","components","overrides","createElement","Fragment","map","component","index","type","key","collection","collectionId","CustomComponent","slots","id","filter","Boolean"],"sources":["../../../../src/components/AutoPatternsCollectionPageContent/AutoPatternsCollectionPageContent.tsx"],"sourcesContent":["import React from 'react';\nimport { CollectionPageConfig } from '../../types';\nimport { usePatternsWizardOverridesContext } from '../../providers';\nimport { AutoPatternsCollectionComponent } from '../AutoPatternsCollectionComponent/AutoPatternsCollectionComponent';\n\nexport interface AutoPatternsCollectionPageContentProps {\n  configuration: CollectionPageConfig;\n}\n\nexport const AutoPatternsCollectionPageContent = ({\n  configuration,\n}: AutoPatternsCollectionPageContentProps) => {\n  const { components } = configuration;\n  const overrides = usePatternsWizardOverridesContext();\n\n  return (\n    <>\n      {components\n        .map((component, index) => {\n          if (component.type === 'collection') {\n            return (\n              <AutoPatternsCollectionComponent\n                key={`collection-${component.collection.collectionId}-${index}`}\n                component={component}\n                index={index}\n              />\n            );\n          } else if (component.type === 'custom') {\n            const CustomComponent = overrides?.slots?.[component.id];\n\n            if (!CustomComponent) {\n              return null;\n            }\n\n            return <CustomComponent key={`custom-${component.id}-${index}`} />;\n          }\n\n          return null;\n        })\n        .filter(Boolean)}\n    </>\n  );\n};\n"],"mappings":"AAAA,OAAOA,KAAK,MAAM,OAAO;AAEzB,SAASC,iCAAiC,QAAQ,iBAAiB;AACnE,SAASC,+BAA+B,QAAQ,oEAAoE;AAMpH,OAAO,MAAMC,iCAAiC,GAAGC,IAAA,IAEH;EAAA,IAFI;IAChDC;EACsC,CAAC,GAAAD,IAAA;EACvC,MAAM;IAAEE;EAAW,CAAC,GAAGD,aAAa;EACpC,MAAME,SAAS,GAAGN,iCAAiC,CAAC,CAAC;EAErD,oBACED,KAAA,CAAAQ,aAAA,CAAAR,KAAA,CAAAS,QAAA,QACGH,UAAU,CACRI,GAAG,CAAC,CAACC,SAAS,EAAEC,KAAK,KAAK;IACzB,IAAID,SAAS,CAACE,IAAI,KAAK,YAAY,EAAE;MACnC,oBACEb,KAAA,CAAAQ,aAAA,CAACN,+BAA+B;QAC9BY,GAAG,EAAE,cAAcH,SAAS,CAACI,UAAU,CAACC,YAAY,IAAIJ,KAAK,EAAG;QAChED,SAAS,EAAEA,SAAU;QACrBC,KAAK,EAAEA;MAAM,CACd,CAAC;IAEN,CAAC,MAAM,IAAID,SAAS,CAACE,IAAI,KAAK,QAAQ,EAAE;MACtC,MAAMI,eAAe,GAAGV,SAAS,EAAEW,KAAK,GAAGP,SAAS,CAACQ,EAAE,CAAC;MAExD,IAAI,CAACF,eAAe,EAAE;QACpB,OAAO,IAAI;MACb;MAEA,oBAAOjB,KAAA,CAAAQ,aAAA,CAACS,eAAe;QAACH,GAAG,EAAE,UAAUH,SAAS,CAACQ,EAAE,IAAIP,KAAK;MAAG,CAAE,CAAC;IACpE;IAEA,OAAO,IAAI;EACb,CAAC,CAAC,CACDQ,MAAM,CAACC,OAAO,CACjB,CAAC;AAEP,CAAC","ignoreList":[]}
+{"version":3,"names":["React","usePatternsWizardOverridesContext","AutoPatternsCollectionComponent","AutoPatternsCollectionPageContent","_ref","configuration","components","overrides","createElement","Fragment","map","component","index","type","key","collection","collectionId","_overrides$slots","CustomComponent","slots","id","filter","Boolean"],"sources":["../../../../src/components/AutoPatternsCollectionPageContent/AutoPatternsCollectionPageContent.tsx"],"sourcesContent":["import React from 'react';\nimport { CollectionPageConfig } from '../../types';\nimport { usePatternsWizardOverridesContext } from '../../providers';\nimport { AutoPatternsCollectionComponent } from '../AutoPatternsCollectionComponent/AutoPatternsCollectionComponent';\n\nexport interface AutoPatternsCollectionPageContentProps {\n  configuration: CollectionPageConfig;\n}\n\nexport const AutoPatternsCollectionPageContent = ({\n  configuration,\n}: AutoPatternsCollectionPageContentProps) => {\n  const { components } = configuration;\n  const overrides = usePatternsWizardOverridesContext();\n\n  return (\n    <>\n      {components\n        .map((component, index) => {\n          if (component.type === 'collection') {\n            return (\n              <AutoPatternsCollectionComponent\n                key={`collection-${component.collection.collectionId}-${index}`}\n                component={component}\n                index={index}\n              />\n            );\n          } else if (component.type === 'custom') {\n            const CustomComponent = overrides?.slots?.[component.id];\n\n            if (!CustomComponent) {\n              return null;\n            }\n\n            return <CustomComponent key={`custom-${component.id}-${index}`} />;\n          }\n\n          return null;\n        })\n        .filter(Boolean)}\n    </>\n  );\n};\n"],"mappings":"AAAA,OAAOA,KAAK,MAAM,OAAO;AAEzB,SAASC,iCAAiC,QAAQ,iBAAiB;AACnE,SAASC,+BAA+B,QAAQ,oEAAoE;AAMpH,OAAO,MAAMC,iCAAiC,GAAGC,IAAA,IAEH;EAAA,IAFI;IAChDC;EACsC,CAAC,GAAAD,IAAA;EACvC,MAAM;IAAEE;EAAW,CAAC,GAAGD,aAAa;EACpC,MAAME,SAAS,GAAGN,iCAAiC,CAAC,CAAC;EAErD,oBACED,KAAA,CAAAQ,aAAA,CAAAR,KAAA,CAAAS,QAAA,QACGH,UAAU,CACRI,GAAG,CAAC,CAACC,SAAS,EAAEC,KAAK,KAAK;IACzB,IAAID,SAAS,CAACE,IAAI,KAAK,YAAY,EAAE;MACnC,oBACEb,KAAA,CAAAQ,aAAA,CAACN,+BAA+B;QAC9BY,GAAG,EAAE,cAAcH,SAAS,CAACI,UAAU,CAACC,YAAY,IAAIJ,KAAK,EAAG;QAChED,SAAS,EAAEA,SAAU;QACrBC,KAAK,EAAEA;MAAM,CACd,CAAC;IAEN,CAAC,MAAM,IAAID,SAAS,CAACE,IAAI,KAAK,QAAQ,EAAE;MAAA,IAAAI,gBAAA;MACtC,MAAMC,eAAe,GAAGX,SAAS,aAAAU,gBAAA,GAATV,SAAS,CAAEY,KAAK,qBAAhBF,gBAAA,CAAmBN,SAAS,CAACS,EAAE,CAAC;MAExD,IAAI,CAACF,eAAe,EAAE;QACpB,OAAO,IAAI;MACb;MAEA,oBAAOlB,KAAA,CAAAQ,aAAA,CAACU,eAAe;QAACJ,GAAG,EAAE,UAAUH,SAAS,CAACS,EAAE,IAAIR,KAAK;MAAG,CAAE,CAAC;IACpE;IAEA,OAAO,IAAI;EACb,CAAC,CAAC,CACDS,MAAM,CAACC,OAAO,CACjB,CAAC;AAEP,CAAC","ignoreList":[]}