@wix/ditto-codegen-public 1.0.142 → 1.0.143

package/dist/out.js

@@ -114863,14 +114863,6 @@ var require_data = __commonJS({
         displayName: "Handling Fees Rules",
         displayField: "productId",
         fields: [
-          {
-            key: "productId",
-            displayName: "Product",
-            type: "REFERENCE",
-            referenceOptions: {
-              referencedCollectionId: "Stores/Products"
-            }
-          },
           { key: "oversizedFee", displayName: "Oversized Fee", type: "NUMBER" },
           { key: "fragileFee", displayName: "Fragile Fee", type: "NUMBER" }
         ],
@@ -114893,12 +114885,10 @@ Your output must be strictly JSON that conforms to the provided schema (no markd
 
 <constraints>
 - Field definitions must use supported FieldType enums exactly as strings: TEXT, NUMBER, DATE, DATETIME, IMAGE, BOOLEAN, DOCUMENT, URL, RICH_TEXT, VIDEO, ANY, ARRAY_STRING, ARRAY_DOCUMENT, AUDIO, TIME, LANGUAGE, RICH_CONTENT, MEDIA_GALLERY, ADDRESS, PAGE_LINK, REFERENCE, MULTI_REFERENCE, OBJECT, ARRAY.
-- ALWAYS use REFERENCE fields when creating relationships between different CMS collections. ALL related fields must use REFERENCE type.
-- ALWAYS use REFERENCE fields when the blueprint indicates relationships to Stores entities (products, categories, orders). Use TEXT fields for all other relationships.
-- MANDATORY REFERENCE scenarios (you MUST use REFERENCE type):
-  - productId, product \u2192 REFERENCE to "Stores/Products"
-  - categoryId, category \u2192 REFERENCE to "Stores/Collections"
-  - orderId, order \u2192 REFERENCE to "Stores/Orders"
+- REFERENCE and MULTI_REFERENCE fields:
+  * ONLY use REFERENCE/MULTI_REFERENCE fields when linking between custom CMS collections defined within this app
+  * The "referencedCollectionId" MUST be the "idSuffix" of another collection you are creating in the same plan
+  * NEVER use REFERENCE fields to link to Wix business entities (Products, Orders, Contacts, Members, etc.)
 - Permissions must use AccessLevel enums exactly as strings: UNDEFINED, ANYONE, SITE_MEMBER, SITE_MEMBER_AUTHOR, CMS_EDITOR, PRIVILEGED. Prefer read: ANYONE, insert/update/remove: PRIVILEGED unless the blueprint implies otherwise.
 - Permissions: For each collection, specify the permissions for each operation (insert, update, remove, read) using one of the following access levels:
   - UNDEFINED: Not set.
@@ -114940,9 +114930,8 @@ For the collections field, return:
 <approach>
 1) Read the blueprint name and summary to infer the domain nouns and essential attributes.
 2) Propose collections only when the blueprint clearly requires persistent data. Define only the fields that are strictly required to fulfill the blueprint's functionality.
-3) For any field that references products, categories, or orders: ALWAYS use REFERENCE type with proper typeMetadata.
-4) Pick clear collection ids derived from the domain, lower-kebab or lower_underscore; avoid spaces.
-5) Avoid Duplicate Data Storage - EMBEDDED SCRIPT CONFIGURATION:
+3) Pick clear collection ids derived from the domain, lower-kebab or lower_underscore; avoid spaces.
+4) Avoid Duplicate Data Storage - EMBEDDED SCRIPT CONFIGURATION:
    - Embedded script parameters (defined in embeddedScriptParameters) are ALREADY saved and persisted via the embeddedScripts
    - NEVER create CMS collections that duplicate these parameters (colors, messages, positions, display settings, coupon codes, headlines, etc.)
    - CMS collections should ONLY be created for additional business data that is NOT covered by embeddedScriptParameters
@@ -114953,7 +114942,7 @@ For the collections field, return:
    - Example (WRONG):
      * Creating both embeddedScriptParameters AND a "popup-configurations" CMS collection - this is duplicate storage
    - Only create CMS collections if there's genuinely new data needed beyond what's in embeddedScriptParameters (e.g., user-generated content, event logs if explicitly requested, business entities)
-6) Initial Data Assessment:
+5) Initial Data Assessment:
    - After defining the collection schema, evaluate if initial/seed data can be implied from the blueprint
    - Consider if the blueprint describes example data, default configurations, sample content, or starter records that would help demonstrate the app's functionality
    - Initial data is appropriate when:
@@ -114964,12 +114953,12 @@ For the collections field, return:
      * The collection is for user-generated content that starts empty
      * The blueprint doesn't mention any example or default data
      * The collection is for transactional/log data that accumulates over time
-7) Initial Data Compliance:
+6) Initial Data Compliance:
    - If initial data is needed, include an "initialData" array in the collection definition
    - Each item in initialData MUST strictly comply with the collection schema:
      * Use the exact field keys defined in the schema (lowerCamelCase)
      * Match field types exactly (TEXT \u2192 string, NUMBER \u2192 number, BOOLEAN \u2192 boolean, DATE/DATETIME \u2192 ISO 8601 string, etc.)
-     * For REFERENCE fields: provide valid reference IDs or leave empty if referencing external collections (Stores/Products, etc.)
+     * For REFERENCE fields: provide valid reference ID of idSuffix of the referenced collection
      * For required fields: always provide values
      * For optional fields: may omit if not needed for the example
    - Initial data should be realistic and representative of actual usage
@@ -118576,11 +118565,47 @@ var require_prompt_selectors = __commonJS({
     "use strict";
     Object.defineProperty(exports2, "__esModule", { value: true });
     exports2.shouldUseDataPrompt = shouldUseDataPrompt;
+    exports2.hasUnsupportedCollectionFieldsTypes = hasUnsupportedCollectionFieldsTypes;
+    exports2.hasUnsupportedCollectionTypes = hasUnsupportedCollectionTypes;
     exports2.shouldUseDynamicParametersPrompt = shouldUseDynamicParametersPrompt;
+    var types_1 = require_types_impl2();
+    var ditto_codegen_types_1 = require_dist();
     function shouldUseDataPrompt(params) {
       const { plan, previousResources } = params;
       return Boolean(plan?.collections?.length || previousResources?.collections?.length);
     }
+    var unsupportedCollectionTypesInAutoPatterns = [
+      types_1.FieldType.MULTI_REFERENCE,
+      types_1.FieldType.OBJECT,
+      types_1.FieldType.ARRAY,
+      types_1.FieldType.DOCUMENT,
+      types_1.FieldType.RICH_TEXT,
+      types_1.FieldType.VIDEO,
+      types_1.FieldType.ANY,
+      types_1.FieldType.ARRAY_DOCUMENT,
+      types_1.FieldType.AUDIO,
+      types_1.FieldType.TIME,
+      types_1.FieldType.LANGUAGE,
+      types_1.FieldType.RICH_CONTENT,
+      types_1.FieldType.MEDIA_GALLERY,
+      types_1.FieldType.ADDRESS
+    ];
+    function hasUnsupportedCollectionFieldsTypes(collection) {
+      return unsupportedCollectionTypesInAutoPatterns.some((type) => collection.fields?.some((field) => field.type === type));
+    }
+    function hasUnsupportedCollectionTypes(params) {
+      const { plan, previousResources } = params;
+      const hasUnsupportedInPreviousCollections = previousResources?.collections?.some((collection) => hasUnsupportedCollectionFieldsTypes(collection));
+      if (hasUnsupportedInPreviousCollections)
+        return true;
+      const hasUnsupportedInPlanCollections = plan?.collections?.some((collection) => {
+        if (collection.operation === ditto_codegen_types_1.ExtensionGenerationOperation.DELETE) {
+          return false;
+        }
+        return hasUnsupportedCollectionFieldsTypes(collection.data);
+      });
+      return Boolean(hasUnsupportedInPlanCollections);
+    }
     function shouldUseDynamicParametersPrompt(params) {
       const { plan, previousResources } = params;
       return Boolean(plan?.embeddedScriptParameters?.length || previousResources?.embeddedScriptParameters?.length);
@@ -120775,7 +120800,8 @@ var require_DashboardDecisionAgent = __commonJS({
         const hasOneDashboardPageExtension = blueprint?.extensions?.filter((ext) => ext.type === types_1.ExtensionType.DASHBOARD_PAGE).length === 1;
         const shouldImplementEmbeddedScriptParameters = hasOneDashboardPageExtension && hasEmbeddedScriptExtension;
         const hasCollections = (0, prompt_selectors_1.shouldUseDataPrompt)(params);
-        if (!hasCollections || shouldImplementEmbeddedScriptParameters) {
+        const hasUnsupportedCollectionFieldsTypes = (0, prompt_selectors_1.hasUnsupportedCollectionTypes)(params);
+        if (!hasCollections || shouldImplementEmbeddedScriptParameters || hasUnsupportedCollectionFieldsTypes) {
           return true;
         }
         return false;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.142",
+  "version": "1.0.143",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -24,5 +24,5 @@
     "@wix/ditto-codegen": "1.0.0",
     "esbuild": "^0.25.9"
   },
-  "falconPackageHash": "2ab41eb85f48c5fa0300400982acd53f1ea7d736736189c67108359a"
+  "falconPackageHash": "e6533be2dac590d9bf241e372b818aac3ebb29c78842c2a142d6e2bd"
 }