@wix/auto-patterns 1.34.0 → 1.35.0

package/mcp-docs/action_cell.md

@@ -40,6 +40,7 @@ Both properties are optional, but at least one should be provided for the Action
      - Browser interactions (alerts, downloads)
      - Complex operations
    - ⚠️ Requires implementation: Must register action in overrides
+   - ⚠️ **CRITICAL: Error Handling Required** - When implementing custom actions that make HTTP requests, you MUST read the "Error Handling for HTTP Requests" section and apply the correct error handling patterns. Wix HTTP requests require `errorHandler.withErrorHandler`, while external API calls should NOT use errorHandler.
 
 ### Action Appearance: The `skin` Property
 
@@ -139,7 +140,7 @@ Custom actions execute JavaScript code that you define. These actions receive pa
            },
            successToast: 'Pet details downloaded',
            errorToast: (err, {retry}) => ({
-             message: 'Download failed',
+             text: 'Download failed',
              action: { text: 'Retry', onClick: retry }
            })
          });
@@ -149,6 +150,53 @@ Custom actions execute JavaScript code that you define. These actions receive pa
    };
    ```
 
+   **⚠️ CRITICAL: Error Handling for HTTP Requests**
+
+   The example above uses SDK methods which don't require error handling. However, if your custom action makes HTTP requests, you MUST follow the error handling patterns:
+
+   **For Wix HTTP requests (httpClient, wix/data, wix/stores):**
+   ```typescript
+   import { errorHandler } from '@wix/essentials';
+
+   export const myAction: CustomActionCellSecondaryActionResolver = (params) => {
+     return {
+       label: 'My Action',
+       icon: <MyIcon />,
+       onClick: () => {
+         // ✅ CORRECT: Wix API call wrapped with errorHandler
+         errorHandler.withErrorHandler(
+           async () => {
+             const response = await httpClient.request(
+               myWixApiCall({ data: params.actionParams.item })
+             );
+             return response.data;
+           },
+           {}
+         );
+       },
+     };
+   };
+   ```
+
+   **For External API requests (fetch, axios, third-party):**
+   ```typescript
+   export const myAction: CustomActionCellSecondaryActionResolver = (params) => {
+     return {
+       label: 'My Action',
+       icon: <MyIcon />,
+       onClick: () => {
+         // ✅ CORRECT: External API call - NO errorHandler needed
+         fetch('https://api.external-service.com/endpoint', {
+           method: 'POST',
+           body: JSON.stringify(params.actionParams.item)
+         });
+       },
+     };
+   };
+   ```
+
+   **Read the "Error Handling for HTTP Requests" section for complete guidance.**
+
 3. Export your action in `actions/index.tsx`:
    ```typescript
    import { downloadPetDetails } from './downloadPetDetails';
@@ -209,7 +257,7 @@ Custom actions execute JavaScript code that you define. These actions receive pa
    - Enable analytics tracking for user interactions
 
 2. The implementation must return a `ResolvedAction` object with:
-   - `label`: Text displayed for the action 
+   - `label`: Text displayed for the action
    - `icon`: An Icon component from "@wix/wix-ui-icons-common"
    - `onClick`: Handler function for the action
    - `biName`: Business intelligence name for analytics tracking. Must match the `biName` in your action configuration (required)