npm - @superblocksteam/vite-plugin-file-sync - Versions diffs - 2.0.43-next.1 → 2.0.43-next.3 - Mend

@superblocksteam/vite-plugin-file-sync 2.0.43-next.1 → 2.0.43-next.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (57) hide show

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/full-examples.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from full-examples.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.044Z
+// Generated at: 2025-10-09T14:20:12.230Z
 export const content = "### FULL EXAMPLES\n\n#### Full example 1:\n\nBelow is a full example of a user's prompt and acceptable app. Note that AppHeader, AppSidebar, MetricCard and Chart components are part of the default set of custom components available in every app.\n\nGiven this prompt:\n\n```text\nCreate a restaurant delivery dashboard with the following features:\n\n- A sidebar with navigation for restaurants, orders, and delivery sections\n- Key metrics displayed as cards showing total orders, active restaurants, active drivers, and average delivery time\n- A chart showing order trends over time\n- A filterable table of restaurants with search by name, cuisine type, and status\n- The ability to edit restaurant details through a modal\n- All data should be dynamically filtered based on user input\n```\n\nFiles generated:\n\n```pages/Page1/scope.ts\nimport {\n  createScope,\n  SbApi,\n  EventFlow,\n  StateVar,\n  computed,\n} from \"@superblocksteam/library\";\nexport const Page1Scope = createScope<{\n  Column1: any;\n  AppSidebar1: any;\n  AppHeader1: any;\n  MetricCard1: any;\n  MetricCard2: any;\n  MetricCard3: any;\n  MetricCard4: any;\n  RevenueChart: any;\n  RestaurantsTable: any;\n  Modal1: any;\n  RestaurantNameInput: any;\n  CuisineTypeDropdown: any;\n  StatusDropdown: any;\n  ResetButton: any;\n  CustomerNameInput: any;\n  PurchaseTypeDropdown: any;\n  CustomersTable: any;\n  ModalRestaurantNameInput: any;\n  ModalRestaurantEmailInput: any;\n  ModalRestaurantOwnerInput: any;\n  ModalRestaurantCuisineDropdown: any;\n  ModalRestaurantStatusDropdown: any;\n}>(\n  ({\n    entities: {\n      Column1,\n      AppSidebar1,\n      AppHeader1,\n      MetricCard1,\n      MetricCard2,\n      MetricCard3,\n      MetricCard4,\n      RevenueChart,\n      RestaurantsTable,\n      Modal1,\n      RestaurantNameInput,\n      CuisineTypeDropdown,\n      StatusDropdown,\n      ResetButton,\n      CustomerNameInput,\n      PurchaseTypeDropdown,\n      CustomersTable,\n      getMetricsApi,\n      getRestaurantsDataApi,\n      ChartDataVar,\n      RestaurantsTableDataVar,\n      ModalRestaurantNameInput,\n      ModalRestaurantEmailInput,\n      ModalRestaurantOwnerInput,\n      ModalRestaurantCuisineDropdown,\n      ModalRestaurantStatusDropdown,\n      updateRestaurantApi,\n    },\n  }) => ({\n    getMetricsApi: SbApi({}),\n    getRestaurantsDataApi: SbApi({}),\n    ChartDataVar: StateVar({\n      defaultValue: computed(() => {\n        const restaurantName =\n          RestaurantNameInput.value && RestaurantNameInput.value !== \"\"\n            ? RestaurantNameInput.value\n            : null;\n        const cuisineType =\n          CuisineTypeDropdown.selectedOptionValue === \"All\"\n            ? null\n            : CuisineTypeDropdown.selectedOptionValue;\n        const status =\n          StatusDropdown.selectedOptionValue === \"All\"\n            ? null\n            : StatusDropdown.selectedOptionValue;\n        let data = getRestaurantsDataApi.response || [];\n\n        data = data.filter((restaurant: any) => {\n          if (\n            restaurantName &&\n            !restaurant.name\n              .toLowerCase()\n              .includes(restaurantName.toLowerCase())\n          ) {\n            return false;\n          }\n          if (cuisineType && restaurant.cuisine !== cuisineType) {\n            return false;\n          }\n          if (status && restaurant.status !== status) {\n            return false;\n          }\n          return true;\n        });\n        const months = [\"Jan\", \"Feb\", \"Mar\", \"Apr\", \"May\", \"Jun\", \"Jul\"];\n        return months.map((month) => {\n          const totalOrders = data.reduce((sum: number, restaurant: any) => {\n            return sum + (restaurant.monthlyOrders[month] || 0);\n          }, 0);\n          return {\n            name: month,\n            orders: totalOrders,\n          };\n        });\n      }),\n    }),\n    RestaurantsTableDataVar: StateVar({\n      defaultValue: computed(() => {\n        const restaurantName =\n          RestaurantNameInput.value && RestaurantNameInput.value !== \"\"\n            ? RestaurantNameInput.value\n            : null;\n        const cuisineType =\n          CuisineTypeDropdown.selectedOptionValue === \"All\"\n            ? null\n            : CuisineTypeDropdown.selectedOptionValue;\n        const status =\n          StatusDropdown.selectedOptionValue === \"All\"\n            ? null\n            : StatusDropdown.selectedOptionValue;\n        let data = getRestaurantsDataApi.response || [];\n\n        data = data.filter((restaurant: any) => {\n          if (\n            restaurantName &&\n            !restaurant.name\n              .toLowerCase()\n              .includes(restaurantName.toLowerCase())\n          ) {\n            return false;\n          }\n          if (cuisineType && restaurant.cuisine !== cuisineType) {\n            return false;\n          }\n          if (status && restaurant.status !== status) {\n            return false;\n          }\n          return true;\n        });\n        return data.map((restaurant: any) => ({\n          photo: restaurant.photo,\n          name: restaurant.name,\n          email: restaurant.email,\n          cuisine: restaurant.cuisine,\n          owner: restaurant.owner,\n          status: restaurant.status,\n          date_joined: restaurant.date_joined,\n          last_activity: restaurant.last_activity,\n        }));\n      }),\n    }),\n    updateRestaurantApi: SbApi({\n      onError: EventFlow.controlModal(Modal1, { action: \"close\" }),\n      onSuccess: EventFlow.runApis([getRestaurantsDataApi]),\n    }),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\nexport const Page1 = Page1Scope.entities;\n```\n\nNote that the layout in the index file here makes use of Container components to logically group sections and ensure everything is spaced out and aligned well.\n\n```pages/Page1/index.tsx\nimport Table from \"components/ui/Table/index\";\nimport Container from \"components/ui/Container/index\";\nimport Input from \"components/ui/Input/index\";\nimport Dropdown from \"components/ui/Dropdown/index\";\nimport Button from \"components/ui/Button/index\";\nimport Modal from \"components/ui/Modal/index\";\nimport Text from \"components/ui/Text/index\";\nimport {\n  Page,\n  Dim,\n  registerPage,\n  computed,\n  EventFlow,\n  Theme,\n} from \"@superblocksteam/library\";\nimport Chart from \"components/Chart/Chart\";\nimport MetricCard from \"components/MetricCard/MetricCard\";\nimport AppHeader from \"components/AppHeader/AppHeader\";\nimport AppSidebar from \"components/AppSidebar/AppSidebar\";\nimport KeyValue from \"components/KeyValue\";\nimport { Page1, Page1Scope } from \"./scope\";\nfunction PageContent() {\n  const {\n    Column1,\n    AppSidebar1,\n    AppHeader1,\n    MetricCard1,\n    MetricCard2,\n    MetricCard3,\n    MetricCard4,\n    RevenueChart,\n    RestaurantsTable,\n    Modal1,\n    RestaurantNameInput,\n    CuisineTypeDropdown,\n    StatusDropdown,\n    ResetButton,\n    CustomerNameInput,\n    PurchaseTypeDropdown,\n    CustomersTable,\n    ModalRestaurantNameInput,\n    ModalRestaurantEmailInput,\n    ModalRestaurantOwnerInput,\n    ModalRestaurantCuisineDropdown,\n    ModalRestaurantStatusDropdown,\n    getMetricsApi,\n    getRestaurantsDataApi,\n    ChartDataVar,\n    RestaurantsTableDataVar,\n    updateRestaurantApi,\n  } = Page1;\n  return (\n    <Page\n      name=\"Page1\"\n      height={Dim.fill()}\n      width={Dim.fill()}\n      onLoad={EventFlow.runApis([getMetricsApi, getRestaurantsDataApi])}\n    >\n      <Section height={Dim.fill()}>\n        <Column\n          width={Dim.fit()}\n          padding={{\n            top: {\n              value: 0,\n              mode: \"px\",\n            },\n            bottom: {\n              value: 0,\n              mode: \"px\",\n            },\n            left: {\n              value: 0,\n              mode: \"px\",\n            },\n            right: {\n              value: 0,\n              mode: \"px\",\n            },\n          }}\n        >\n          <AppSidebar\n            width={Dim.fill()}\n            bind={AppSidebar1}\n            logoUrl=\"your-app-logo-url.png\"\n            sidebarLinks={[\n              {\n                header: \"Restaurants\",\n                links: [\n                  {\n                    label: \"All Restaurants\",\n                    icon: \"restaurant\",\n                  },\n                  {\n                    label: \"Onboarding\",\n                    icon: \"add_business\",\n                  },\n                ],\n              },\n              {\n                header: \"Orders\",\n                links: [\n                  {\n                    label: \"Active Orders\",\n                    icon: \"receipt_long\",\n                  },\n                  {\n                    label: \"Order History\",\n                    icon: \"history\",\n                  },\n                ],\n              },\n              {\n                header: \"Delivery\",\n                links: [\n                  {\n                    label: \"Drivers\",\n                    icon: \"directions_car\",\n                  },\n                  {\n                    label: \"Live Tracking\",\n                    icon: \"map\",\n                  },\n                  {\n                    label: \"Analytics\",\n                    icon: \"analytics\",\n                  },\n                ],\n              },\n            ]}\n            height={Dim.fill()}\n          />\n        </Column>\n        <Column\n          width={Dim.fill()}\n          bind={Column1}\n          padding={{\n            top: {\n              value: 0,\n              mode: \"px\",\n            },\n            bottom: {\n              value: 0,\n              mode: \"px\",\n            },\n            left: {\n              value: 0,\n              mode: \"px\",\n            },\n            right: {\n              value: 0,\n              mode: \"px\",\n            },\n          }}\n          spacing={Dim.px(0)}\n        >\n          <AppHeader\n            width={Dim.fill()}\n            height={Dim.fit()}\n            bind={AppHeader1}\n            title=\"Delivery Dashboard\"\n            avatarUrl=\"your-user-avatar-here.png\"\n            userEmail=\"user@workdoamin.com\"\n          />\n          <Container\n            width={Dim.fill()}\n            height={Dim.fill()}\n            layout=\"vertical\"\n            padding={{\n              top: {\n                value: 12,\n                mode: \"px\",\n              },\n              bottom: {\n                value: 12,\n                mode: \"px\",\n              },\n              left: {\n                value: 12,\n                mode: \"px\",\n              },\n              right: {\n                value: 12,\n                mode: \"px\",\n              },\n            }}\n          >\n            <Container\n              width={Dim.fill()}\n              height={Dim.fit()}\n              layout=\"horizontal\"\n            >\n              <MetricCard\n                width={Dim.fill()}\n                height={Dim.fill()}\n                bind={MetricCard1}\n                title=\"Total Orders\"\n                value={computed(\n                  () => getMetricsApi.response?.totalOrders.value,\n                )}\n                changeValue={computed(\n                  () => getMetricsApi.response?.totalOrders.changeValue,\n                )}\n                changeType={getMetricsApi.response?.totalOrders.changeType}\n                icon=\"receipt_long\"\n              />\n              <MetricCard\n                width={Dim.fill()}\n                height={Dim.fill()}\n                bind={MetricCard2}\n                title=\"Active Restaurants\"\n                value={computed(\n                  () => getMetricsApi.response?.activeRestaurants.value,\n                )}\n                changeValue={\n                  getMetricsApi.response?.activeRestaurants.changeValue\n                }\n                changeType={\n                  getMetricsApi.response?.activeRestaurants.changeType\n                }\n                icon=\"restaurant\"\n              />\n              <MetricCard\n                width={Dim.fill()}\n                height={Dim.fill()}\n                bind={MetricCard3}\n                title=\"Active Drivers\"\n                value={computed(\n                  () => getMetricsApi.response?.activeDrivers.value,\n                )}\n                changeValue={getMetricsApi.response?.activeDrivers.changeValue}\n                changeType={getMetricsApi.response?.activeDrivers.changeType}\n                icon=\"directions_car\"\n              />\n              <MetricCard\n                width={Dim.fill()}\n                height={Dim.fill()}\n                bind={MetricCard4}\n                title=\"Avg Delivery Time\"\n                value={getMetricsApi.response?.avgDeliveryTime.value}\n                changeType={getMetricsApi.response?.avgDeliveryTime.changeType}\n                icon=\"schedule\"\n                changeValue={computed(\n                  () => getMetricsApi.response?.avgDeliveryTime.changeValue,\n                )}\n              />\n            </Container>\n            <Chart\n              width={Dim.fill()}\n              height={Dim.px(180)}\n              bind={RevenueChart}\n              title=\"Orders\"\n              data={computed(() => ChartDataVar.value || [])}\n            />\n            <Container\n              width={Dim.fill()}\n              height={Dim.fit()}\n              variant=\"card\"\n              layout=\"horizontal\"\n              verticalAlign=\"bottom\"\n            >\n              <Input\n                label=\"Restaurant Name\"\n                placeholderText=\"Search restaurants...\"\n                bind={RestaurantNameInput}\n              />\n              <Dropdown\n                label=\"Cuisine Type\"\n                options={[\n                  {\n                    label: \"All\",\n                    value: \"All\",\n                  },\n                  {\n                    label: \"Italian\",\n                    value: \"Italian\",\n                  },\n                  {\n                    label: \"Chinese\",\n                    value: \"Chinese\",\n                  },\n                  {\n                    label: \"Mexican\",\n                    value: \"Mexican\",\n                  },\n                  {\n                    label: \"American\",\n                    value: \"American\",\n                  },\n                ]}\n                defaultValue=\"All\"\n                bind={CuisineTypeDropdown}\n              />\n              <Dropdown\n                label=\"Status\"\n                options={[\n                  {\n                    label: \"All\",\n                    value: \"All\",\n                  },\n                  {\n                    label: \"Online\",\n                    value: \"Online\",\n                  },\n                  {\n                    label: \"Offline\",\n                    value: \"Offline\",\n                  },\n                  {\n                    label: \"Busy\",\n                    value: \"Busy\",\n                  },\n                ]}\n                defaultValue=\"All\"\n                bind={StatusDropdown}\n              />\n              <Button\n                label=\"Reset Filters\"\n                bind={ResetButton}\n                onClick={EventFlow.runJS(() => {\n                  RestaurantNameInput.text = \"\";\n                  CuisineTypeDropdown.value = \"All\";\n                  StatusDropdown.value = \"All\";\n                })}\n              />\n            </Container>\n            <Table\n              width={Dim.fill()}\n              height={Dim.fit()}\n              tableData={computed(() => RestaurantsTableDataVar.value || [])}\n              columns={{\n                name: {\n                  columnType: \"text\",\n                  label: \"Restaurant\",\n                },\n                email: {\n                  columnType: \"email\",\n                  label: \"Email\",\n                },\n                cuisine: {\n                  columnType: \"text\",\n                  label: \"Cuisine\",\n                },\n                owner: {\n                  columnType: \"text\",\n                  label: \"Owner\",\n                },\n                status: {\n                  columnType: \"tags\",\n                  tagDisplayConfig: {\n                    Online: {\n                      color: \"#14CDB733\",\n                    },\n                    Busy: {\n                      color: \"#FF9F3533\",\n                    },\n                    Offline: {\n                      color: \"#a6a0a033\",\n                    },\n                  },\n                  label: \"Status\",\n                },\n                date_joined: {\n                  columnType: \"date\",\n                  inputFormat: \"YYYY-MM-DD\",\n                  outputFormat: \"MM-DD-YYYY\",\n                  label: \"Date joined\",\n                },\n                last_activity: {\n                  columnType: \"date\",\n                  inputFormat: \"YYYY-MM-DDTHH:mm:ssZ\",\n                  outputFormat: \"MM-DD-YYYY\",\n                  label: \"Last activity\",\n                },\n                photo: {\n                  columnType: \"image\",\n                  label: \"Photo\",\n                  imageBorderRadius: {\n                    topLeft: {\n                      mode: \"px\",\n                      value: 16,\n                    },\n                    topRight: {\n                      mode: \"px\",\n                      value: 16,\n                    },\n                    bottomLeft: {\n                      mode: \"px\",\n                      value: 16,\n                    },\n                    bottomRight: {\n                      mode: \"px\",\n                      value: 16,\n                    },\n                  },\n                },\n              }}\n              header=\"Restaurants\"\n              isSearchable={false}\n              bind={RestaurantsTable}\n              onRowClick={EventFlow.runJS(() => {\n                // set values of all the modal inputs to the values of the selected row\n                ModalRestaurantNameInput.text =\n                  RestaurantsTable.selectedRow?.name;\n                ModalRestaurantEmailInput.text =\n                  RestaurantsTable.selectedRow?.email;\n                ModalRestaurantOwnerInput.text =\n                  RestaurantsTable.selectedRow?.owner;\n                ModalRestaurantCuisineDropdown.value =\n                  RestaurantsTable.selectedRow?.cuisine;\n                ModalRestaurantStatusDropdown.value =\n                  RestaurantsTable.selectedRow?.status;\n              }).controlModal(Modal1, { action: \"open\" })}\n              paginationType=\"client-side\"\n              configuredPageSize={10}\n            />\n          </Container>\n        </Column>\n      </Section>\n      <Modal\n        width={Dim.fill()}\n        height={Dim.fit()}\n        bind={Modal1}\n        spacing={Dim.px(0)}\n        padding={{\n          top: {\n            value: 0,\n            mode: \"px\",\n          },\n          bottom: {\n            value: 0,\n            mode: \"px\",\n          },\n          left: {\n            value: 0,\n            mode: \"px\",\n          },\n          right: {\n            value: 0,\n            mode: \"px\",\n          },\n        }}\n      >\n        <Container\n          variant=\"none\"\n          width={Dim.fill()}\n          layout=\"vertical\"\n          spacing={Dim.px(4)}\n          horizontalAlign=\"left\"\n          padding={{\n            top: {\n              value: 16,\n              mode: \"px\",\n            },\n            bottom: {\n              value: 16,\n              mode: \"px\",\n            },\n            left: {\n              value: 16,\n              mode: \"px\",\n            },\n            right: {\n              value: 16,\n              mode: \"px\",\n            },\n          }}\n          border={{\n            left: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n            right: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n            top: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n            bottom: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 1,\n              },\n              style: \"solid\",\n            },\n          }}\n        >\n          <Text\n            text={computed(() => {\n              return RestaurantsTable.selectedRow?.name || \"Restaurant Details\";\n            })}\n            textStyle={{\n              variant: \"heading3\",\n            }}\n          />\n        </Container>\n        <Container\n          variant=\"none\"\n          width={Dim.fill()}\n          horizontalAlign=\"left\"\n          padding={{\n            top: {\n              value: 16,\n              mode: \"px\",\n            },\n            bottom: {\n              value: 16,\n              mode: \"px\",\n            },\n            left: {\n              value: 16,\n              mode: \"px\",\n            },\n            right: {\n              value: 16,\n              mode: \"px\",\n            },\n          }}\n        >\n          {/* <Text\n            text={computed(() => {\n              return `Joined ${RestaurantsTable.selectedRow?.date_joined} and last active ${RestaurantsTable.selectedRow?.last_activity}`;\n            })}\n            textStyle={{\n              variant: \"body2\",\n            }}\n            isVisible={computed(() => {\n              return (\n                RestaurantsTable.selectedRow?.date_joined !== undefined &&\n                RestaurantsTable.selectedRow?.last_activity !== undefined\n              );\n            })}\n           /> */}\n\n          <Input label=\"Restaurant Name\" bind={ModalRestaurantNameInput} />\n          <Input label=\"Email\" bind={ModalRestaurantEmailInput} />\n          <Input label=\"Owner\" bind={ModalRestaurantOwnerInput} />\n          <Dropdown\n            label=\"Cuisine\"\n            options={[\n              {\n                label: \"Italian\",\n                value: \"Italian\",\n              },\n              {\n                label: \"Chinese\",\n                value: \"Chinese\",\n              },\n              {\n                label: \"Mexican\",\n                value: \"Mexican\",\n              },\n              {\n                label: \"American\",\n                value: \"American\",\n              },\n            ]}\n            bind={ModalRestaurantCuisineDropdown}\n          />\n          <Dropdown\n            label=\"Status\"\n            options={[\n              {\n                label: \"Online\",\n                value: \"Online\",\n              },\n              {\n                label: \"Offline\",\n                value: \"Offline\",\n              },\n              {\n                label: \"Busy\",\n                value: \"Busy\",\n              },\n            ]}\n            bind={ModalRestaurantStatusDropdown}\n          />\n        </Container>\n        <Container\n          spacing={Dim.px(8)}\n          width={Dim.fill()}\n          variant=\"none\"\n          layout=\"horizontal\"\n          horizontalAlign=\"right\"\n          padding={{\n            top: {\n              value: 16,\n              mode: \"px\",\n            },\n            bottom: {\n              value: 16,\n              mode: \"px\",\n            },\n            left: {\n              value: 16,\n              mode: \"px\",\n            },\n            right: {\n              value: 16,\n              mode: \"px\",\n            },\n          }}\n          border={{\n            left: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n            right: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n            top: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 1,\n              },\n              style: \"solid\",\n            },\n            bottom: {\n              color: Theme.colors.neutral100,\n              width: {\n                mode: \"px\",\n                value: 0,\n              },\n              style: \"solid\",\n            },\n          }}\n        >\n          <Button\n            label=\"Close\"\n            variant=\"secondary\"\n            onClick={EventFlow.controlModal(Modal1, { action: \"close\" })}\n          />\n          <Button\n            label=\"Save Changes\"\n            onClick={EventFlow.runApis([updateRestaurantApi]).controlModal(\n              Modal1,\n              { action: \"close\" },\n            )}\n          />\n        </Container>\n      </Modal>\n    </Page>\n  );\n}\nexport default registerPage(PageContent, Page1Scope);\n```\n\n```pages/Page1/apis/getMetricsApi.ts\nimport {\n  Api,\n  Athena,\n  BigQuery,\n  DynamoDb,\n  JavaScript,\n  Python,\n  Databricks,\n  MicrosoftSql,\n  MySql,\n  Snowflake,\n  PostgreSQL,\n  RestApi,\n  Email,\n  Salesforce,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"getMetricsApi\", [\n  new JavaScript(\"getMetrics\", {\n    fn: () => {\n      return {\n        totalOrders: {\n          value: \"24.7K\",\n          changeValue: \"+18.2%\",\n          changeType: \"positive\",\n        },\n        activeRestaurants: {\n          value: \"1.8K\",\n          changeValue: \"+12.5%\",\n          changeType: \"positive\",\n        },\n        activeDrivers: {\n          value: \"523\",\n          changeValue: \"+5.8%\",\n          changeType: \"positive\",\n        },\n        avgDeliveryTime: {\n          value: \"28 min\",\n          changeValue: \"-2.3 min\",\n          changeType: \"positive\",\n        },\n      };\n    },\n  }),\n]);\n```\n\n```pages/Page1/apis/getRestaurantsDataApi.ts\nimport {\n  Api,\n  Athena,\n  BigQuery,\n  DynamoDb,\n  JavaScript,\n  Python,\n  Databricks,\n  MicrosoftSql,\n  MySql,\n  Snowflake,\n  PostgreSQL,\n  RestApi,\n  Email,\n  Salesforce,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"getRestaurantsDataApi\", [\n  new JavaScript(\"getData\", {\n    fn: () => {\n      return [\n        {\n          photo: \"https://images.unsplash.com/photo-1517248135467-4c7edcad34c4?w=50&h=50&fit=crop&crop=face\",\n          name: \"Bella Vista Italian\",\n          email: \"contact@bellavista.com\",\n          cuisine: \"Italian\",\n          owner: \"Marco Rossi\",\n          status: \"Active\",\n          date_joined: \"2023-01-15\",\n          last_activity: \"2024-01-20\",\n          monthlyOrders: {\n            Jan: 450,\n            Feb: 520,\n            Mar: 480,\n            Apr: 610,\n            May: 590,\n            Jun: 650,\n            Jul: 720,\n          },\n        },\n        {\n          photo: \"https://images.unsplash.com/photo-1555396273-367ea4eb4db5?w=50&h=50&fit=crop&crop=face\",\n          name: \"Golden Dragon\",\n          email: \"info@goldendragon.com\",\n          cuisine: \"Chinese\",\n          owner: \"Wei Chen\",\n          status: \"Active\",\n          date_joined: \"2023-02-22\",\n          last_activity: \"2024-01-19\",\n          monthlyOrders: {\n            Jan: 380,\n            Feb: 420,\n            Mar: 460,\n            Apr: 510,\n            May: 540,\n            Jun: 580,\n            Jul: 620,\n          },\n        },\n        {\n          photo: \"https://images.unsplash.com/photo-1565299624946-b28f40a0ca4b?w=50&h=50&fit=crop&crop=face\",\n          name: \"Taco Fiesta\",\n          email: \"orders@tacofiesta.com\",\n          cuisine: \"Mexican\",\n          owner: \"Carlos Rodriguez\",\n          status: \"Pending\",\n          date_joined: \"2023-12-10\",\n          last_activity: \"2024-01-18\",\n          monthlyOrders: {\n            Jan: 280,\n            Feb: 320,\n            Mar: 350,\n            Apr: 390,\n            May: 420,\n            Jun: 450,\n            Jul: 480,\n          },\n        },\n        {\n          photo: \"https://images.unsplash.com/photo-1571091718767-18b5b1457add?w=50&h=50&fit=crop&crop=face\",\n          name: \"Burger Palace\",\n          email: \"hello@burgerpalace.com\",\n          cuisine: \"American\",\n          owner: \"John Smith\",\n          status: \"Active\",\n          date_joined: \"2022-11-08\",\n          last_activity: \"2024-01-21\",\n          monthlyOrders: {\n            Jan: 680,\n            Feb: 720,\n            Mar: 650,\n            Apr: 780,\n            May: 810,\n            Jun: 850,\n            Jul: 920,\n          },\n        },\n        {\n          photo: \"https://images.unsplash.com/photo-1414235077428-338989a2e8c0?w=50&h=50&fit=crop&crop=face\",\n          name: \"Sakura Sushi\",\n          email: \"reservations@sakurasushi.com\",\n          cuisine: \"Japanese\",\n          owner: \"Takeshi Yamamoto\",\n          status: \"Inactive\",\n          date_joined: \"2023-06-12\",\n          last_activity: \"2023-12-15\",\n          monthlyOrders: {\n            Jan: 320,\n            Feb: 280,\n            Mar: 260,\n            Apr: 240,\n            May: 200,\n            Jun: 180,\n            Jul: 150,\n          },\n        },\n      ];\n    },\n  }),\n]);\n```\n\n```pages/Page1/apis/updateRestaurantApi.ts\nimport {\n  Api,\n  Athena,\n  BigQuery,\n  DynamoDb,\n  JavaScript,\n  Python,\n  Databricks,\n  MicrosoftSql,\n  MySql,\n  Snowflake,\n  PostgreSQL,\n  RestApi,\n  Email,\n  Salesforce,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"updateRestaurantApi\", [\n  new Conditional(\"validate_inputs\", {\n    if: {\n      when: ({\n        ModalRestaurantNameInput,\n        ModalRestaurantEmailInput,\n        ModalRestaurantOwnerInput,\n      }): boolean =>\n        !ModalRestaurantNameInput.value ||\n        !ModalRestaurantEmailInput.value ||\n        !ModalRestaurantOwnerInput.value,\n      then: [\n        new Throw(\"validation_error\", {\n          error: \"Restaurant name, email, and owner are required fields\",\n        }),\n      ],\n    },\n  }),\n  new JavaScript(\"updateRestaurantData\", {\n    fn: ({\n      ModalRestaurantNameInput,\n      ModalRestaurantEmailInput,\n      ModalRestaurantOwnerInput,\n      ModalRestaurantCuisineDropdown,\n      ModalRestaurantStatusDropdown,\n    }) => {\n      const updatedRestaurant = {\n        name: ModalRestaurantNameInput.value,\n        email: ModalRestaurantEmailInput.value,\n        cuisine: ModalRestaurantCuisineDropdown.selectedOptionValue,\n        owner: ModalRestaurantOwnerInput.value,\n        status: ModalRestaurantStatusDropdown.selectedOptionValue,\n        updated_at: new Date().toISOString(),\n      };\n\n      return {\n        success: true,\n        message: \"Restaurant updated successfully\",\n        data: updatedRestaurant,\n      };\n    },\n  }),\n]);\n```\n\n##### Important notes about the choices made in the code generated here:\n\n1. **API Implementation Strategy**: All APIs use dummy data implementations for demonstration purposes. In production applications:\n   - `getMetricsApi` and `getRestaurantsDataApi` should connect to actual databases or external services using SQL queries, REST API calls, or other data connectors\n   - `updateRestaurantApi` should perform real database updates or API calls to persist changes\n   - Consider replacing dummy implementations with actual integrations when users specify particular data sources in their prompts\n\n2. **Layout Architecture**:\n   - `Column` components have padding removed to allow `AppSidebar` and `AppHeader` to extend to screen edges\n   - Content sections use `Container` components for proper spacing and alignment\n   - This pattern ensures consistent visual hierarchy and responsive behavior\n\n3. **Component Styling Patterns**:\n   - Filter controls are wrapped together in a `Container` with `variant=\"card\"` to provide visual containment\n   - Components like `MetricCard`, `Table`, and `Chart` have built-in containers and don't require additional wrapping\n   - Form elements (`Input`, `Dropdown`, `Button`) need explicit container styling for proper presentation\n\n4. **State Management**:\n   - Computed variables (`ChartDataVar`, `RestaurantsTableDataVar`) automatically recalculate when filter inputs change\n   - Modal state is managed through event flows that handle open/close actions and API responses\n   - Error handling and validation are implemented at the API level with appropriate user feedback\n";
 //# sourceMappingURL=full-examples.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-api.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-api.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.043Z
+// Generated at: 2025-10-09T14:20:12.229Z
 export const content = "### APIs\n\nThe Superblocks framework allows you to create backend APIs. The high level structure for creating APIs is as follows:\n\n1. APIs are defined using TypeScript files that live inside the apis directory inside the page they are scoped to. Example: /pages/Page1/apis/myApi.ts\n2. This pattern is a declarative workflow builder, where you define each API step, its configuration, and its execution order within the API workflow.\n3. To make the API available for use, you must import it into the scope file and register it with `SbApi()`, then import and destructure it in your page component for use.\n4. **CRITICAL INTEGRATION RULE**:\n   - DO NOT create API steps with integrations that require a configuration ID (PostgreSQL, Snowflake, Databricks, etc.) unless you have been explicitly provided with valid integration configuration IDs\n   - NEVER make up or hallucinate integration IDs like \"postgres-integration-id\", a uuid, or similar placeholder strings\n   - User mentions like \"@some-intgration-name\" or \"use the postgres database\" do NOT constitute valid integration configurations. You must match the user's request to a valid integration configuration\n   - The only integrations that do not require a configuration are: JavaScript, Python, Conditional, TryCatch, Variables, Loop, Parallel, Wait, Throw, Return\n   - If a user requests integration functionality but no valid integration configurations have been provided, you can ignore that part of their request and in your description of what you've built, add that there was no integration configuration provided for their request\n   - Only use integration IDs that appear in the explicitly provided list of integration configurations\n\n#### CRITICAL VARIABLE SCOPING RULES\n\n**🚨 EXTREMELY IMPORTANT**: Variables referenced in API blocks can ONLY come from these sources:\n\n1. **Outputs of previous blocks** in the same API (accessed via the block name)\n2. **Page entities defined in the scope file** (passed as destructured parameters)\n3. **Never reference variables that don't exist** - this is the #1 cause of API generation errors\n\n**❌ WRONG - Variables that don't exist in scope:**\n\n```ts\nnew PostgreSQL(\"insert_data\", \"postgres-integration-id\", {\n  statement: ({ SelectedCustomerIdVar, ProductNameInput, IssueTypeDropdown }) =>\n    `INSERT INTO issues VALUES (${SelectedCustomerIdVar.value}, '${ProductNameInput.value}', '${IssueTypeDropdown.selectedOptionValue}')`,\n  // ❌ ERROR: SelectedCustomerIdVar, ProductNameInput, IssueTypeDropdown are not defined anywhere!\n});\n```\n\n**✅ CORRECT - Variables from scope entities:**\n\n```ts\n// First, define in scope.ts:\nexport const Page1Scope = createScope<{\n  SelectedCustomerIdVar: any;\n  ProductNameInput: any;\n  IssueTypeDropdown: any;\n}>(\n  () => ({\n    // Register the API\n    submitIssueApi: SbApi({}),\n  }),\n  { name: \"Page1\" },\n);\n\n// Then use in API:\nnew PostgreSQL(\"insert_data\", \"postgres-integration-id\", {\n  statement: ({ SelectedCustomerIdVar, ProductNameInput, IssueTypeDropdown }) =>\n    `INSERT INTO issues VALUES (${SelectedCustomerIdVar.value}, '${ProductNameInput.value}', '${IssueTypeDropdown.selectedOptionValue}')`,\n  // ✅ CORRECT: These are page entities defined in the scope\n});\n```\n\n**✅ CORRECT - Variables from previous blocks:**\n\n```ts\nexport default new Api(\"processOrderApi\", [\n  new JavaScript(\"get_customer_data\", {\n    fn: () => ({ customerId: 123, customerName: \"John Doe\" }),\n  }),\n  new PostgreSQL(\"insert_order\", \"postgres-integration-id\", {\n    statement: ({ get_customer_data }) =>\n      `INSERT INTO orders VALUES (${get_customer_data.output.customerId}, '${get_customer_data.output.customerName}')`,\n    // ✅ CORRECT: get_customer_data is a previous block in this API\n  }),\n]);\n```\n\n#### Variables Block Value Access\n\nWhen you use the Variables control block inside an API, you must access the defined variableds with their value via `{variableFromVariablesBlock}.value` — always.\n\n- ✅ Correct: `variableFromVariablesBlock.value`\n- ❌ Wrong: `variableFromVariablesBlock`\n- ❌ Wrong: `variableFromVariablesBlock.output`\n\nExample using Variables with a REST step:\n\n```ts\nexport default new Api(\"fetchUserByIdApi\", [\n  // Capture a value into a variable via Variables block\n  new Variables(\"selected_user_id_var\", [\n    {\n      key: \"selectedUserIdVar\",\n      value: ({ UserIdInput }) => UserIdInput.value,\n    },\n  ]),\n\n  // Use the Variables block value with .value in subsequent steps\n  // Note how we don't access via the Variabls block name, just the direct name of the variable defined inside the Variables block\n  new RestApi(\"get_user\", {\n    method: \"GET\",\n    path: ({ selectedUserIdVar }) => `/api/users/${selectedUserIdVar.value}`,\n  }),\n]);\n```\n\nA good mental check: If you created the value with a Variables block, read it with `.value` on the variable name. Do not use `.output` and do not omit `.value`.\n\n#### Control block variables (.value)\n\nVariables introduced by control-flow blocks are accessed via `.value` — always.\n\n- Loop: if you define variables `{ item: \"item\", index: \"index\" }`, access them as `item.value` and `index.value`\n- Parallel: if you define variables `{ item: \"item\" }`, access it as `item.value`\n- TryCatch: if you define `{ variables: { error: \"error\" } }`, access it as `error.value`\n\nExamples:\n\n```ts\nexport default new Api(\"processApi\", [\n  new Loop(\"for_each_order\", {\n    over: ({ retrieve_orders }) => retrieve_orders.output,\n    variables: { item: \"order\", index: \"i\" },\n    blocks: [\n      new JavaScript(\"process\", {\n        fn: ({ order, i }) => ({\n          id: order.value.id,\n          position: i.value,\n        }),\n      }),\n    ],\n  }),\n\n  new Parallel(\"fetch_user_details\", {\n    over: ({ userIds }) => userIds.value,\n    variables: { item: \"userId\" },\n    blocks: [\n      new RestApi(\"get_user\", {\n        method: \"GET\",\n        path: ({ userId }) => `/api/users/${userId.value}`,\n      }),\n    ],\n  }),\n\n  new TryCatch(\"wrap\", {\n    variables: { error: \"err\" },\n    try: [\n      new JavaScript(\"doSomething\", {\n        fn: () => {\n          /* ... */\n        },\n      }),\n    ],\n    catch: [\n      new JavaScript(\"onError\", {\n        fn: ({ err }) => ({ message: String(err.value) }),\n      }),\n    ],\n  }),\n]);\n```\n\nULTRA CRITICAL: Always access control-block variables (Loop, Parallel, TryCatch) via `.value` when reading their values or properties.\n\n- ✅ Correct: `item.value`, `item.value.id`, `index.value`, `error.value`\n- ❌ Wrong: `item`, `item.id`, `index`, `error`\n\nWhen you customize variable names, the same rule applies. For example, if you set `variables: { item: \"auditItem\", index: \"auditIndex\" }`, then:\n\n- ✅ Correct: `auditItem.value.id`, `auditIndex.value`\n- ❌ Wrong: `auditItem.id`, `auditIndex`\n\nPutting it together in a REST path:\n\n```ts\nnew RestApi(\"fetchAudit\", {\n  method: \"GET\",\n  path: ({ auditItem, auditIndex }) =>\n    `https://api.example.com/audit/${auditItem.value.id}/${auditIndex.value}`,\n});\n```\n\n#### CRITICAL MENTAL MODEL: APIs Access Page Scope (They Don't Define Parameters)\n\n**🚨 FUNDAMENTAL MISCONCEPTION TO AVOID:**\n\n❌ **WRONG THINKING**: \"APIs define their input parameters like traditional backend services\"\n\n```ts\n// WRONG - This is NOT how Superblocks APIs work!\nfunction submitOrder(customerId, productName) {\n  // ❌ APIs don't define parameters!\n  // API logic here\n}\n```\n\n✅ **CORRECT THINKING**: \"APIs are frontend-coupled functions that automatically access the page's existing scope\"\n\n```ts\n// CORRECT - APIs inherit page scope automatically\nnew PostgreSQL(\"insert_order\", \"postgres-integration-id\", {\n  statement: ({ SelectedCustomerIdVar, ProductNameInput }) =>\n    // ↑ This is NOT defining parameters - this is accessing existing page scope!\n    // These variables must ALREADY exist in your page scope\n    `INSERT INTO orders VALUES (${SelectedCustomerIdVar.value}, '${ProductNameInput.value}')`,\n});\n```\n\n**KEY CONCEPTS:**\n\n1. **APIs are frontend-aware**: They're tightly coupled to your page, not independent backend services\n2. **No parameter definition**: APIs cannot define their own input parameters\n3. **Scope inheritance only**: APIs automatically access whatever exists in your page scope\n4. **Mandatory order**: Page Scope → Components → APIs (scope must exist first)\n\n**The Flow:**\n\n```\nPage Scope Variables → APIs Automatically Access → Use in API Logic\n(Must exist first)   → (No parameter passing)   → (Just destructure from scope)\n```\n\n**Contrasting Examples:**\n\n❌ **Traditional Backend API (NOT how Superblocks works):**\n\n```ts\n// This is how traditional APIs work - NOT Superblocks!\nfunction createOrder(customerId, productName, quantity) {\n  // ❌ Defines own parameters\n  return database.insert({\n    customer_id: customerId,\n    product: productName,\n    qty: quantity,\n  });\n}\n\n// Called like: createOrder(123, \"Widget\", 5) - parameters passed in\n```\n\n✅ **Superblocks API (Frontend-coupled):**\n\n```ts\n// This is how Superblocks APIs work - inherits page scope\nnew PostgreSQL(\"insert_order\", \"postgres-integration-id\", {\n  statement: ({ CustomerIdInput, ProductNameInput, QuantityInput }) => {\n    // ↑ NOT defining parameters! These must exist in page scope already\n    return `INSERT INTO orders VALUES (${CustomerIdInput.value}, '${ProductNameInput.value}', ${QuantityInput.value})`;\n  },\n});\n\n// No \"calling with parameters\" - scope variables are automatically available\n```\n\n#### Rules\n\n1. CRITICAL: The name of the API must be consistent across the API's TypeScript definition, the API's file name, references in page files, and the key used to register it in the scope file. See the consistent use of 'myApi' below as an example.\n2. ALWAYS import ALL API classes from the superblocks library at the top of every API file. Use this complete import statement for every API file:\n3. When using database integrations (PostgreSQL, Snowflake, Databricks), the integration_id parameter should be the actual integration ID from your Superblocks workspace, not a placeholder string.\n4. **CRITICAL**: DO NOT reference variables that are not in scope. The ONLY things in scope are (1) the outputs of previous blocks that are in lexical scope and (2) page entities defined in the scope file.\n\n```ts\nimport {\n  Api,\n  JavaScript,\n  Python,\n  Databricks,\n  Snowflake,\n  PostgreSQL,\n  GraphQL,\n  RestApi,\n  Email,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n  Break,\n} from \"@superblocksteam/library\";\n```\n\n#### Examples\n\n##### Complete Example: Scope → Components → API Flow\n\nThis example shows the complete flow from defining variables in scope, to binding them to components, to using them in APIs.\n\n**Step 1: Define entities in scope file**\n\n```ts\n// /pages/Page1/scope.ts\nimport { createScope, SbApi } from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  CustomerNameInput: any;\n  ProductNameInput: any;\n  IssueTypeDropdown: any;\n  IssueNotesInput: any;\n}>(\n  () => ({\n    // Register the API\n    submitProductIssueApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n**Step 2: Use entities in page components**\n\n```tsx\n// /pages/Page1/index.tsx\nimport {\n  Page,\n  Container,\n  Input,\n  Dropdown,\n  Button,\n  EventFlow,\n  registerPage,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const {\n    CustomerNameInput,\n    ProductNameInput,\n    IssueTypeDropdown,\n    IssueNotesInput,\n    submitProductIssueApi,\n  } = Page1;\n\n  return (\n    <Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        <Input bind={CustomerNameInput} label=\"Customer Name\" />\n        <Input bind={ProductNameInput} label=\"Product Name\" />\n        <Dropdown\n          bind={IssueTypeDropdown}\n          label=\"Issue Type\"\n          options={[\n            { label: \"Defect\", value: \"defect\" },\n            { label: \"Complaint\", value: \"complaint\" },\n            { label: \"Return\", value: \"return\" },\n          ]}\n        />\n        <Input bind={IssueNotesInput} label=\"Notes\" multiline={true} />\n        <Button\n          label=\"Submit Issue\"\n          onClick={EventFlow.runApis([submitProductIssueApi])}\n        />\n      </Container>\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n**Step 3: Create API that uses the scope entities**\n\n```ts\n// /pages/Page1/apis/submitProductIssueApi.ts\n\nimport {\n  Api,\n  JavaScript,\n  Python,\n  Databricks,\n  Snowflake,\n  PostgreSQL,\n  GraphQL,\n  RestApi,\n  Email,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n  Break,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"submitProductIssueApi\", [\n  new Conditional(\"validate_inputs\", {\n    if: {\n      when: ({\n        CustomerNameInput,\n        ProductNameInput,\n        IssueTypeDropdown,\n      }): boolean =>\n        !CustomerNameInput.value ||\n        !ProductNameInput.value ||\n        !IssueTypeDropdown.selectedOptionValue,\n      then: [\n        new Throw(\"validation_error\", {\n          error: \"Customer name, product name, and issue type are required\",\n        }),\n      ],\n    },\n  }),\n  new PostgreSQL(\"insert_issue\", \"your-postgresql-integration-id\", {\n    statement: ({\n      CustomerNameInput,\n      ProductNameInput,\n      IssueTypeDropdown,\n      IssueNotesInput,\n    }) =>\n      `INSERT INTO product_issues\n       (customer_name, product_name, issue_type, notes, status, date_reported, created_by)\n       VALUES (\n         '${CustomerNameInput.value}',\n         '${ProductNameInput.value}',\n         '${IssueTypeDropdown.selectedOptionValue}',\n         '${IssueNotesInput.value || \"\"}',\n         'Open',\n         NOW(),\n         1\n       )`,\n  }),\n  new JavaScript(\"return_success\", {\n    fn: ({ insert_issue }) => ({\n      success: true,\n      message: \"Issue submitted successfully\",\n      issueId: insert_issue.output?.insertId || null,\n    }),\n  }),\n]);\n```\n\n##### ❌ COMMON MISTAKES TO AVOID\n\n**❌ WRONG: Using undefined variables**\n\n```ts\n// This is WRONG - these variables don't exist!\nexport default new Api(\"badExampleApi\", [\n  new PostgreSQL(\"insert_data\", \"postgres-integration-id\", {\n    statement: ({\n      SelectedCustomerIdVar,\n      ProductNameInput,\n      IssueTypeDropdown,\n    }) =>\n      `INSERT INTO issues VALUES (${SelectedCustomerIdVar.value}, '${ProductNameInput.value}', '${IssueTypeDropdown.selectedOptionValue}')`,\n    // ❌ ERROR: SelectedCustomerIdVar, ProductNameInput, IssueTypeDropdown are not defined in scope!\n  }),\n]);\n```\n\n**❌ WRONG: Mixing up variable names**\n\n```ts\n// Scope defines CustomerNameInput but API tries to use CustomerName\nexport default new Api(\"badExampleApi\", [\n  new PostgreSQL(\"insert_data\", \"postgres-integration-id\", {\n    statement: (\n      { CustomerName }, // ❌ ERROR: Should be CustomerNameInput\n    ) => `INSERT INTO issues VALUES ('${CustomerName.value}')`,\n  }),\n]);\n```\n\n**❌ WRONG: Not destructuring function parameters**\n\n```ts\n// This is WRONG - you must destructure the parameters\nexport default new Api(\"badExampleApi\", [\n  new PostgreSQL(\"insert_data\", \"postgres-integration-id\", {\n    statement: (\n      state, // ❌ ERROR: Should destructure { CustomerNameInput }\n    ) => `INSERT INTO issues VALUES ('${state.CustomerNameInput.value}')`,\n  }),\n]);\n```\n\n##### Creating and registering a Superblocks API\n\nCreate the API by adding the myApi.ts file:\n\n```ts\n// /pages/Page1/apis/myApi.ts\n\nimport {\n  Api,\n  JavaScript,\n  Python,\n  Databricks,\n  Snowflake,\n  PostgreSQL,\n  GraphQL,\n  RestApi,\n  Email,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n  Break,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"myApi\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: \"ORD-001\",\n          customerName: \"John Smith\",\n          total: 149.99,\n        },\n        {\n          id: \"ORD-002\",\n          customerName: \"Sarah Jones\",\n          total: 89.5,\n        },\n      ];\n    },\n  }),\n]);\n```\n\nThen register the myApi API in the scope file:\n\n```ts\n// /pages/Page1/scope.ts\n\nimport { createScope, SbApi } from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope(\n  () => ({\n    // Register the API in the scope\n    retrieveOrdersApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\nThen use the API in your page component:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport {\n  Page,\n  Container,\n  Button,\n  Table,\n  computed,\n  EventFlow,\n  registerPage,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const { retrieveOrdersApi } = Page1;\n\n  return (\n    <Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        <Button\n          // APIs can be invoked with the EventFlow API\n          onClick={EventFlow.runApis([retrieveOrdersApi])}\n          label=\"Fetch Data\"\n        />\n        {/* Access API response using computed */}\n        <Table tableData={computed(() => retrieveOrdersApi.response)} />\n      </Container>\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n##### Referencing the output of a previous block\n\nThink hard about how you access the output of previous steps. You MUST use the output property of the previous step variable. There is no other way to access the output of a previous step (other than using a Variable block, but that is not what you want in this case and should only be used in very specific cases).\n\n```ts\n// Path to this api would be: /pages/Page1/apis/getOrdersApi.ts\n\nimport {\n  Api,\n  JavaScript,\n  Python,\n  Databricks,\n  Snowflake,\n  PostgreSQL,\n  GraphQL,\n  RestApi,\n  Email,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n  Break,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"getOrdersApi\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: 1,\n          customer: \"John Smith\",\n          date: \"2024-01-15\",\n          total: 199.99,\n          status: \"Pending\",\n        },\n        {\n          id: 2,\n          customer: \"Jane Doe\",\n          date: \"2024-01-14\",\n          total: 149.99,\n          status: \"Shipped\",\n        },\n        {\n          id: 3,\n          customer: \"Bob Wilson\",\n          date: \"2024-01-13\",\n          total: 299.99,\n          status: \"Delivered\",\n        },\n      ];\n    },\n  }),\n  new JavaScript(\"format_orders\", {\n    fn: ({ retrieve_orders }) => {\n      return retrieve_orders.output.map((order) => ({\n        ...order,\n        date: new Date(order.date).toLocaleDateString(),\n      }));\n    },\n  }),\n]);\n```\n\nThen you would register the API in your scope file and use it in your page component:\n\n```ts\n// /pages/Page1/scope.ts\nexport const Page1Scope = createScope(\n  () => ({\n    getOrdersApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\n// /pages/Page1/index.tsx\nimport {\n  Page,\n  Container,\n  Table,\n  computed,\n  registerPage,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const { getOrdersApi } = Page1;\n\n  return (\n    <Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n      <Container width={Dim.fill()} height={Dim.fill()}>\n        <Table tableData={computed(() => getOrdersApi.response)} />\n      </Container>\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n##### Ensuring variable existence in application\n\n**🚨 CRITICAL**: APIs cannot create their own variables - they only access what already exists in page scope!\n\nWhen creating an API that references variables like `FirstNameInput`, `LastNameInput`, and `SelectedUserIdVar`, these variables MUST exist in your page scope BEFORE you write the API. APIs don't define parameters - they inherit scope.\n\n**Mandatory Flow: Scope → Components → APIs**\n\n**STEP 1: Create variables in scope FIRST** (APIs cannot access variables that don't exist)\n\nSince you've determined that we'll use input components to take in the first name and last name, you MUST ensure that you use the same names for the entities in the `scope.ts` file as the variable names in the API.\n\n```ts\n// /pages/Page1/scope.ts\n\nimport {\n  createScope,\n  SbApi,\n  StateVar,\n  StateVarPersistence,\n  Global,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  FirstNameInput: any;\n  LastNameInput: any;\n}>(\n  // register non-component entities in the scope\n  ({\n    entities: {\n      FirstNameInput,\n      LastNameInput,\n      handlePeopleUpdates,\n      SelectedUserIdVar,\n    },\n  }) => ({\n    handlePeopleUpdatesApi: SbApi({}),\n    SelectedUserIdVar: StateVar({\n      defaultValue: Global.user?.id,\n      persistence: StateVarPersistence.TEMPORARY,\n    }),\n  }),\n  // configure page options\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\nThen, use the variables in your page component:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport Input from \"components/ui/Input/index\";\nimport { Page, EventFlow, registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const {\n    handlePeopleUpdatesApi,\n    FirstNameInput,\n    LastNameInput,\n    SelectedUserIdVar,\n  } = Page1;\n\n  return (\n    <Page name=\"Page1\">\n      <Input\n        label=\"First Name\"\n        bind={FirstNameInput}\n        minLength={1}\n        inputType=\"TEXT\"\n      />\n      <Input\n        label=\"Last Name\"\n        bind={LastNameInput}\n        minLength={1}\n        inputType=\"TEXT\"\n      />\n      {/* The rest of the page... */}\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nFinally, create the API that references these variables:\n\n```ts\n// /pages/Page1/apis/handlePeopleUpdatesApi.ts\n\nimport {\n  Api,\n  JavaScript,\n  Python,\n  Databricks,\n  Snowflake,\n  PostgreSQL,\n  GraphQL,\n  RestApi,\n  Email,\n  Conditional,\n  TryCatch,\n  Variables,\n  Loop,\n  Parallel,\n  Throw,\n  Return,\n  Break,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"handlePeopleUpdatesApi\", [\n  new Conditional(\"validate\", {\n    if: {\n      when: ({ FirstNameInput, LastNameInput }): boolean =>\n        !FirstNameInput.isValid || !LastNameInput.isValid,\n      then: [\n        new Throw(\"reject\", {\n          error: \"either the first name or last name is invalid\",\n        }),\n      ],\n    },\n  }),\n  new PostgreSQL(\"update\", \"your-postgresql-integration-id\", {\n    statement: ({ FirstNameInput, LastNameInput, SelectedUserIdVar }) =>\n      `UPDATE people SET first_name = '${FirstNameInput.value}', last_name = '${LastNameInput.value}' WHERE id = ${SelectedUserIdVar.value}`,\n  }),\n]);\n```\n\n#### The Superblocks API TypeScript Type\n\nBelow is the full TypeScript spec for the APIs you create:\n\n````ts\n// @superblocksteam/library\n\nexport type JsonValue =\n  | undefined\n  | null\n  | number\n  | string\n  | boolean\n  | JsonValue[]\n  | object;\nexport type State = { [key: string]: JsonValue };\nexport type Binding<T> = T | ((state: State) => T);\ntype Integrations = { id: string; description: string; metadata: JsonValue }[];\n\nclass Block {\n  constructor(name: string) {}\n  public run(): { output: JsonValue } {\n    /* ... */\n  }\n}\n\nclass Integration extends Block {\n  constructor(name: string, integration_id: string) {}\n}\n\ntype State = Record<string, JsonValue>;\n\nclass JavaScript extends Integration {\n  constructor(\n    name: string,\n    config: {\n      fn: (\n        {\n          /* ... */\n        },\n      ) => JsonValue;\n    },\n  ) {\n    super(name, \"javascript\");\n  }\n}\n\nclass Python extends Integration {\n  constructor(\n    name: string,\n    config: {\n      // We want to just put the python function body here. The scope is the same as it would be if it were a JavaScript integration.\n      fn: string;\n    },\n  ) {\n    super(name, \"python\");\n  }\n}\n\nclass Databricks extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass Athena extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      sqlBody: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass BigQuery extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      sqlBody: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass DynamoDb extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name                       The name of the block.\n   * @param {string} integration_id             The id of the integration.\n   * @param {object} config                     The config object.\n   * @param {string} config.action              The DynamoDB action to perform.\n   * @param {Binding<string>} config.paramsJson A string binding containing a JSON object\n   *                                            with parameters specific to the selected action.\n   *                                            For example: '{\"TableName\": \"MyTable\", \"Key\": {...}}'\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      action:\n        | \"getItem\"\n        | \"updateItem\"\n        | \"putItem\"\n        | \"batchWriteItem\"\n        | \"deleteItem\"\n        | \"query\"\n        | \"scan\"\n        | \"executeStatement\"\n        | \"executeTransaction\"\n        | \"listTagsOfResource\"\n        | \"tagResource\"\n        | \"listTables\"\n        | \"describeTable\"\n        | \"createTable\"\n        | \"updateTable\"\n        | \"deleteTable\";\n      paramsJson: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass Snowflake extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass PostgreSQL extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass MicrosoftSql extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass MariaDB extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass MySQL extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\ntype SalesforceAction =\n  | { action: \"SOQL_ACTION_SOQL\"; soqlBody: Binding<string> }\n  | {\n      action: \"CRUD_ACTION_READ\";\n      resourceType: Binding<string>;\n      resourceId: Binding<string>;\n    }\n  | {\n      action: \"CRUD_ACTION_CREATE\";\n      resourceType: Binding<string>;\n      resourceBody: Binding<string>;\n    }\n  | {\n      action: \"CRUD_ACTION_UPDATE\";\n      resourceType: Binding<string>;\n      resourceId: Binding<string>;\n      resourceBody: Binding<string>;\n    }\n  | {\n      action: \"CRUD_ACTION_DELETE\";\n      resourceType: Binding<string>;\n      resourceId: Binding<string>;\n      resourceBody: Binding<string>;\n    }\n  | {\n      action: \"BULK_ACTION_CREATE\";\n      resourceType: Binding<string>;\n      resourceBody: Binding<string>;\n    }\n  | {\n      action: \"BULK_ACTION_UPDATE\";\n      resourceType: Binding<string>;\n      resourceBody: Binding<string>;\n    };\n\nexport class Salesforce extends Integration {\n  private action: SalesforceAction;\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object containing a SalesforceAction.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      action: SalesforceAction;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass GraphQL extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      query: Binding<string>;\n      variables?: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass RestApi extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    // If you need to make a request that is detached from an integration, you MUST set this to \"restapi\".\n    integration: string = \"restapi\",\n    config: {\n      method: string;\n      url: Binding<string>;\n      // 🚨 IMPORTANT: Headers and params NEED to be arrays of keys and values. For example:\n      // headers: [{ key: \"Authorization\", value: ({ userKey }: { userKey: any }) => userKey.value }]\n      //\n      // Omit them if you cannot follow this rule.\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass GitHub extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Jira extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Airtable extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Anthropic extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Asana extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Bitbucket extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Box extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass CircleCI extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Cohere extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Datadog extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Dropbox extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Elasticsearch extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Fireworks extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Front extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Gemini extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass GoogleAnalytics extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass GoogleDrive extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Groq extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass HubSpot extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Intercom extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass LaunchDarkly extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Mistral extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Notion extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass PagerDuty extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Perplexity extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Segment extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass SendGrid extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Slack extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass StabilityAI extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Stripe extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Twilio extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Zendesk extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Zoom extends RestApi {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  constructor(\n    name: string,\n    integration: string,\n    config: {\n      method: string;\n      url: Binding<string>;\n      headers?: { key: Binding<string>; value: Binding<string> }[];\n      params?: { key: Binding<string>; value: Binding<string> }[];\n      body?: Binding<string>;\n    },\n    openapi?: {\n      /**\n       * This is the path exactly as it appears in the OpenAPI spec.\n       *\n       * For example, if we had the following OpenAPI specification.\n       *\n       * paths:\n       *   /resources/{id}:\n       *     get: # ...\n       *\n       * If you determine that this is the path we should use, then the path would be \"/resources/{id}\".\n       */\n      path: string;\n    },\n  ) {\n    super(name, integration);\n  }\n}\n\nclass Email extends Integration {\n  constructor(\n    name: string,\n    config: {\n      from: Binding<string>;\n      to: Binding<string>;\n      subject: Binding<string>;\n      cc?: Binding<string>;\n      bcc?: Binding<string>;\n      body?: Binding<string>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nexport type Condition = {\n  when: boolean | ((state: State) => boolean);\n  then: Block[];\n};\n\nexport type Conditions = {\n  if: Condition;\n  elif?: Condition[];\n  else?: Block[];\n};\n\nclass Conditional extends Block {\n  constructor(name: string, config: Conditions) {\n    super(name);\n  }\n}\n\nclass TryCatch extends Block {\n  constructor(\n    name: string,\n    config: {\n      try: Block[];\n      catch: Block[];\n      finally?: Block[];\n      variables: { error: string };\n    },\n  ) {\n    super(name);\n  }\n}\n\n/**\n * A Superblocks variable has the following access pattern:\n *\n * How to retrieve the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.value\n *\n * // INCORRECT\n * my_variable\n * ```\n *\n * How to set the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.set(value)\n *\n * // INCORRECT\n * my_variable = value\n * ```\n *\n * When the variable is created via a Variables control block inside an API,\n * you must also reference the block name with `.value` in downstream steps.\n *\n * ```ts\n * // Variables block creates a variable\n * new Variables(\"date_range_var\", [{ key: \"start\", value: StartDatePicker.value }])\n *\n * // Later step MUST access with .value\n * new RestApi(\"fetch\", { path: ({ date_range_var }) => `/api?start=${date_range_var.value}` })\n * ```\n *\n */\n\nclass Variables extends Block {\n  constructor(\n    name: string,\n    variables: {\n      // The name of the variable.\n      key: string;\n      // The value of the variable.\n      value: Binding<JsonValue>;\n    }[],\n  ) {\n    super(name);\n  }\n}\n\nclass Loop extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n        // What the variable name for the current index is.\n        index: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Parallel extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Throw extends Block {\n  constructor(\n    name: string,\n    config: {\n      error: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Return extends Block {\n  constructor(\n    name: string,\n    config: {\n      data: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Break extends Block {\n  constructor(\n    name: string,\n    config: {\n      condition: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Api {\n  constructor(\n    name: string,\n    steps: Block[],\n    authorization:\n      | {\n          type: \"AUTHORIZATION_TYPE_APP_USERS\";\n        }\n      | {\n          type: \"AUTHORIZATION_TYPE_JS_EXPRESSION\";\n          expression: Binding<boolean>;\n        } = { type: \"AUTHORIZATION_TYPE_APP_USERS\" },\n  ) {\n    /* ... */\n  }\n  public get response(): JsonValue {\n    /* ... */\n  }\n  public get error(): string | undefined {\n    /* ... */\n  }\n  public run(): void {\n    /* ... */\n  }\n  public cancel(): void {\n    /* ... */\n  }\n}\n````\n\n#### Rules for using Superblocks APIs\n\nThink hard about the following important rules for correctly using Superblocks APIs:\n\n- You MUST use a destructured object to access page scope variables in dynamic block fields. This syntax is NOT defining function parameters - it's accessing the inherited page scope.\n\n```ts\n// CORRECT: destructuring to access page scope variables that must already exist\n({ Dropdown1, TextInput1 }) => Dropdown1.selectedOptionsValue + TextInput1.value\n// ↑ These variables (Dropdown1, TextInput1) must exist in your page scope!\n\n// INCORRECT: trying to use scope object directly\n(state) => state.Dropdown1.selectedOptionsValue + state.TextInput1.value\n// ↑ This syntax doesn't work in Superblocks\n```\n\n- DO NOT reference variables that are not in scope or that don't exist. The ONLY things in scope are (1) the outputs of previous blocks that are in lexical scope and (2) page entities.\n\n- The result of each scope is the result of the last block in that scope. In the following example, the value of `sendEmail.response` is the result of the `return_summary` block. Use this information to carefully ensure that the last block in your API is the one that returns the value you want.\n\n```ts\nexport default new Api(\"sendEmailApi\", [\n  new Email(\"send_email\", {\n    from: \"noreply@company.com\",\n    to: \"test@test.com\",\n    subject: \"Test Email\",\n    body: \"This is a test email\",\n  }),\n  new JavaScript(\"return_summary\", {\n    fn: () => \"Email sent successfully!\",\n  }),\n]);\n```\n\n- Block outputs are immutable. Do not mutate the output of a block.\n\n- You cannot set Superblocks state variables inside an API\n  ❌ DON'T: Set Superblocks state variableds inside an API.\n  Example:\n\n```\nnew Api(\"addUserApi\", [\n  new JavaScript(\"generateMockUser\", {\n    fn: ({ UsersData }) => {\n      // Generate a new mock user\n      const newUser = {\n        id: Math.floor(Math.random() * 10000) + 1000,\n        name: `User ${Math.floor(Math.random() * 1000)}`,\n        email: `user${Math.floor(Math.random() * 1000)}@example.com`,\n      };\n      // Add the new user to the existing data\n      const updatedUsers = [...UsersData.value, newUser];\n\n      // Update the state variable\n      UsersData.setValue(updatedUsers);\n      return {\n        success: true,\n        message: \"User added successfully\",\n        newUser: newUser,\n        totalUsers: updatedUsers.length,\n\n    };\n   },\n }),\n]);\n```\n\n✅ DO: Set state variables in the APIs onSuccess in the scope file with an EventFlow:\n\nExample:\n\n```\nimport { createScope, StateVar, StateVarPersistence, SbApi, EventFlow } from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  MainTable: any;\n}>(({ entities }) => ({ addUserApi, UsersData }), {\n  name: \"Page1\",\n  UsersData: StateVar({\n    persistence: StateVarPersistence.TEMPORARY,\n    defaultValue: [],\n  }),\n  addUserApi: SbApi({\n    onSuccess: EventFlow.setStateVar(UsersData, [...UsersData.value, addUserApi.response])\n  }),\n});\n```\n\n- You cannot set properties of frontend UI components inside an API\n\n- APIs are registered in scope files using `SbApi()` and then accessed in page components by destructuring from the scope entities. Make sure you name the key used in registerScope the same as the imported API, but do not pass the imported Api into the SbApi() call.\n\n- To access API responses in your UI, use `computed(() => apiName.response)` or `computed(() => apiName.error)`.\n\n- You will not always be told which integrations to use in your API; you will have to determine that yourself based on the data you need to fetch.\n\n- Never add comments to code you (the ai) generate. User added comments are fine - leave those!\n\n#### Breaking Out of Loops\n\n**🚨 CRITICAL**: The Break block is the ONLY way to exit a loop in Superblocks APIs. You cannot use any other method.\n\n**Break block syntax:**\n\n```ts\nnew Break(\"exit_loop\", {\n  condition: ({ item }) => item.value.status === \"complete\",\n});\n```\n\n**✅ CORRECT - Use Break to exit loops:**\n\n```ts\nnew Loop(\"process_items\", {\n  over: ({ items }) => items.output,\n  variables: { item: \"current\", index: \"i\" },\n  blocks: [\n    new Conditional(\"check_stop\", {\n      if: {\n        when: ({ current }) => current.value.status === \"error\",\n        then: [new Break(\"exit_on_error\", { condition: () => true })],\n      },\n    }),\n    new JavaScript(\"process\", { fn: ({ current }) => current.value }),\n  ],\n});\n```\n\n**❌ WRONG - These will NOT exit just the loop:**\n\n```ts\n// JavaScript return does NOT exit the loop\nnew JavaScript(\"wrong\", {\n  fn: () => {\n    return;\n  },\n});\n\n// Return exits the ENTIRE API, not just the loop\nnew Return(\"wrong\", { data: () => \"exit\" });\n\n// Throw stops the ENTIRE API with an error, not just the loop\nnew Throw(\"wrong\", { error: \"exit\" });\n```\n\n**Remember:** Break is the ONLY way to exit a loop and continue with the rest of the API. Return and Throw exit the entire API.\n";
 //# sourceMappingURL=superblocks-api.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-components-rules.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-components-rules.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.043Z
+// Generated at: 2025-10-09T14:20:12.229Z
 export const content = "### Superblocks Component Rules:\n\n**Component Behavior:**\n\n- Never use `computed()` as React children - it returns an object React cannot render\n  - Wrong: `<Container>{computed(() => dynamicText)}</Container>`\n  - Correct: `<Text text={computed(() => dynamicText)} />`\n- Define component property values inline for visual editor compatibility (not in variables)\n- Modal components include a default close button\n\n**Computed Usage:**\n\n- Use `computed()` only for dynamic data (state variables, API responses, component values, theme)\n- Access patterns:\n  - Scope entities: `computed(() => entityName.value)`\n  - Bound components: `computed(() => ComponentName.property)`\n  - Globals: `computed(() => Global.user?.name)` or `computed(() => Theme.colors.primary)`\n- Do not use for static configuration (table columns, static dropdown options, non-dynamic styles)\n\n**Component-Specific:**\n\n- Page component: only add `onLoad` prop\n- Container: use `variant=\"card\"` for white background/padding/border styling\n- EventFlow: use the EventFlow builder when you see _EventFlow_\n";
 //# sourceMappingURL=superblocks-components-rules.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-custom-components.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-custom-components.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.043Z
+// Generated at: 2025-10-09T14:20:12.229Z
 export const content = "# Custom Components\n\n**Core Rules:**\n\n- Never use Superblocks components inside custom components\n- Use existing custom components first before creating new ones\n- Always import React: `import * as React from 'react'`\n- Check `components/` directory for default components that handle common use cases\n- Preserve existing custom component internals unless modification is required\n\n**Visual Editor Integration:**\nCustom components can be made visually editable using the `Prop` API and `registerComponent` function.\n\n**Key APIs:**\n\n- `Prop`: Defines editable properties with types, defaults, and labels\n- `registerComponent`: Connects React component with editable schema for visual editor\n- `useUpdateProperties`: Hook to update properties programmatically during runtime\n\n**Basic Pattern:**\n\n```tsx\nimport {\n  CustomComponentProps,\n  Prop,\n  registerComponent,\n  useUpdateProperties,\n} from \"@superblocksteam/library\";\n\nconst properties = {\n  value: Prop.number().default(3).propertiesPanel({ label: \"Default value\" }),\n  onChange: Prop.event().propertiesPanel({ label: \"On change\" }),\n};\n\ntype ComponentProps = CustomComponentProps<typeof properties>;\n\nconst MyComponent = ({ value, onChange }: ComponentProps) => {\n  const updateProperties = useUpdateProperties();\n\n  return (\n    <div>\n      {/* Component implementation */}\n      <button\n        onClick={() => {\n          updateProperties({ value: newValue });\n          onChange?.();\n        }}\n      >\n        Update\n      </button>\n    </div>\n  );\n};\n\nexport default registerComponent(\"MyComponent\", properties, MyComponent);\n```\n\n**Prop Types:** `Prop.string()`, `Prop.number()`, `Prop.boolean()`, `Prop.event()`, `Prop.any()`, `Prop.composite({...})`, `Prop.record({...})`, `Prop.union({...})`\n\n**Prop Methods:** `.default(value)`, `.propertiesPanel({ label: \"Label\" })`, `.validate(fn)`, `.readable()`, `.writable()`\n\n**Notes:**\n\n- All registered components automatically support `width` and `height` using `Dim` object\n";
 //# sourceMappingURL=superblocks-custom-components.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-data-filtering.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-data-filtering.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.043Z
+// Generated at: 2025-10-09T14:20:12.229Z
 export const content = "# Data Filtering Best Practices\n\n**🚨 CRITICAL: When implementing data filtering, remember that computed cannot be used as React children.** All dynamic filtered content must be passed to component properties like `tableData={}`, `text={}`, etc. Never use `{computed(...)}` as children.\n\nWhen filtering data from APIs or state variables, follow these patterns to keep component properties clean and maintainable:\n\n## When to Use Reactive State Variables for Filtering\n\n**Use reactive state variables with `defaultValue` for complex filtering when:**\n\n- The filtering logic is more than 1-2 lines of code\n- Multiple conditions need to be evaluated\n- Multiple form controls affect the same filtered dataset\n- The logic would make component properties hard to read in the visual editor\n\n**Keep simple filtering in component properties when:**\n\n- The filtering is 1-2 lines of basic logic\n- It's a straightforward filter operation\n- Only one control affects the filtering\n\n## Good Pattern: Reactive State Variables with defaultValue\n\n```tsx\n// First, define component bindings in scope.ts\nexport const Page1Scope = createScope<{\n  OrderSearchInput: any;\n  StatusFilterDropdown: any;\n  DateFromPicker: any;\n  DateToPicker: any;\n}>(\n  ({ entities: { OrderSearchInput, StatusFilterDropdown, DateFromPicker, DateToPicker, getOrdersApi } }) => ({\n    getOrdersApi: SbApi({}),\n    // Define reactive state variable with complex filtering logic in defaultValue\n    filteredOrdersVar: StateVar({\n      defaultValue: computed(() => {\n        return getOrdersApi.response?.filter(order => {\n          const matchesSearch = OrderSearchInput.value === '' ||\n            order.customerName.toLowerCase().includes(OrderSearchInput.value.toLowerCase()) ||\n            order.id.toLowerCase().includes(OrderSearchInput.value.toLowerCase());\n          const matchesStatus = StatusFilterDropdown.selectedOptionValue === 'All' ||\n            order.status === StatusFilterDropdown.selectedOptionValue;\n          const matchesDateRange = !DateFromPicker.value || !DateToPicker.value ||\n            (new Date(order.orderDate) >= new Date(DateFromPicker.value) &&\n             new Date(order.orderDate) <= new Date(DateToPicker.value));\n          return matchesSearch && matchesStatus && matchesDateRange;\n        }) || [];\n      })\n    }),\n  }),\n  { name: \"Page1\" }\n);\n\n// In the component, destructure and use bind properties\nconst { OrderSearchInput, StatusFilterDropdown, DateFromPicker, DateToPicker, filteredOrdersVar } = Page1;\n\n// Clean component properties - just reference the reactive state variable\n<Table tableData={computed(() => filteredOrdersVar.value)} />\n\n// Form controls use bind properties - no onChange logic needed\n<Input\n  bind={OrderSearchInput}\n  placeholder=\"Search orders...\"\n/>\n\n<Dropdown\n  bind={StatusFilterDropdown}\n  options={[\n    { value: 'All', label: 'All Statuses' },\n    { value: 'Processing', label: 'Processing' },\n    { value: 'Shipped', label: 'Shipped' },\n    { value: 'Delivered', label: 'Delivered' }\n  ]}\n/>\n\n<DatePicker bind={DateFromPicker} />\n<DatePicker bind={DateToPicker} />\n```\n\n## Bad Pattern: Duplicated Filtering Logic in Event Handlers\n\n```tsx\n// Avoid this - duplicates filtering logic in every event handler\n<Input\n  placeholder=\"Search orders...\"\n  onChange={EventFlow([\n    (value) => {\n      const filtered = getOrdersApi.response?.filter(order => {\n        const matchesSearch = value === '' ||\n          order.customerName.toLowerCase().includes(value.toLowerCase()) ||\n          order.id.toLowerCase().includes(value.toLowerCase());\n        const matchesStatus = statusFilterVar.value === 'All' || order.status === statusFilterVar.value;\n        const matchesDateRange = !dateFromVar.value || !dateToVar.value ||\n          (new Date(order.orderDate) >= new Date(dateFromVar.value) &&\n           new Date(order.orderDate) <= new Date(dateToVar.value));\n        return matchesSearch && matchesStatus && matchesDateRange;\n      }) || [];\n      filteredOrdersVar.setValue(filtered);\n    }\n  ])}\n/>\n\n<Dropdown\n  onChange={EventFlow([\n    (value) => {\n      // Same filtering logic repeated here - this is what we want to avoid\n      const filtered = getOrdersApi.response?.filter(order => {\n        const matchesSearch = searchTermVar.value === '' ||\n          order.customerName.toLowerCase().includes(searchTermVar.value.toLowerCase());\n        const matchesStatus = value === 'All' || order.status === value;\n        return matchesSearch && matchesStatus;\n      }) || [];\n      filteredOrdersVar.setValue(filtered);\n    }\n  ])}\n/>\n```\n\n## Bad Pattern: Complex Filtering in Component Properties\n\n```tsx\n// Avoid this - complex logic in component property makes visual editor cluttered\n<Table\n  tableData={computed(\n    () =>\n      getOrdersApi.response?.filter((order) => {\n        const matchesSearch =\n          searchTermVar.value === \"\" ||\n          order.customerName\n            .toLowerCase()\n            .includes(searchTermVar.value.toLowerCase()) ||\n          order.id.toLowerCase().includes(searchTermVar.value.toLowerCase());\n        const matchesStatus =\n          statusFilterVar.value === \"All\" ||\n          order.status === statusFilterVar.value;\n        const matchesDateRange =\n          !dateFromVar.value ||\n          !dateToVar.value ||\n          (new Date(order.orderDate) >= new Date(dateFromVar.value) &&\n            new Date(order.orderDate) <= new Date(dateToVar.value));\n        return matchesSearch && matchesStatus && matchesDateRange;\n      }) || [],\n  )}\n/>\n```\n\n## Acceptable: Simple Filtering in Component Properties\n\n```tsx\n// This is fine - simple, straightforward filtering\n<Table tableData={computed(() => getOrdersApi.response?.filter(order => order.status === 'Active') || [])} />\n<Text text={computed(() => `Total: ${getOrdersApi.response?.length || 0}`)} />\n```\n\n## Pattern for Non-Table Components\n\nThis pattern applies to all components, not just tables:\n\n```tsx\n// In scope.ts - define component binding and reactive state variable\nexport const Page1Scope = createScope<{\n  CategoryDropdown: any;\n}>(\n  ({ entities: { CategoryDropdown } }) => ({\n    rawDataVar: StateVar({ defaultValue: [] }),\n    // Good: Complex calculation in reactive state variable\n    summaryTextVar: StateVar({\n      defaultValue: computed(() => {\n        const filteredData = rawDataVar.value?.filter(item => item.category === CategoryDropdown.selectedOptionValue) || [];\n        const total = filteredData.reduce((sum, item) => sum + item.amount, 0);\n        const average = filteredData.length > 0 ? total / filteredData.length : 0;\n        return `${CategoryDropdown.selectedOptionValue} category: ${filteredData.length} items, Total: $${total.toFixed(2)}, Average: $${average.toFixed(2)}`;\n      })\n    }),\n  }),\n  { name: \"Page1\" }\n);\n\n// In component - destructure and use bind\nconst { CategoryDropdown, summaryTextVar } = Page1;\n\n// Clean component property - just references reactive state variable\n<Text text={computed(() => summaryTextVar.value)} />\n\n// Form control uses bind property - no onChange needed\n<Dropdown\n  bind={CategoryDropdown}\n  options={[\n    { value: 'Electronics', label: 'Electronics' },\n    { value: 'Clothing', label: 'Clothing' },\n    { value: 'Books', label: 'Books' }\n  ]}\n/>\n```\n\n## Dynamic Dropdown Options from API Data\n\nWhen you need to create dropdown filters based on actual values from your API response (like filtering by status, category, type, etc.), extract the unique values from the API data to populate dropdown options dynamically.\n\n**Use this pattern when:**\n\n- You want to filter on a property that exists in your API data\n- The possible values for that property are not known in advance\n- You want the dropdown to show only values that actually exist in the data\n\n```tsx\n// In scope.ts - define component bindings and reactive state variables\nexport const Page1Scope = createScope<{\n  StatusFilterDropdown: any;\n  CategoryFilterDropdown: any;\n}>(\n  ({ entities: { StatusFilterDropdown, CategoryFilterDropdown, getProductsApi } }) => ({\n    getProductsApi: SbApi({}),\n\n    // Generate unique status options from API data\n    statusOptionsVar: StateVar({\n      defaultValue: computed(() => {\n        if (!getProductsApi.response) return [{ value: 'All', label: 'All Statuses' }];\n\n        const uniqueStatuses = [...new Set(getProductsApi.response.map(product => product.status))]\n          .filter(status => status) // Remove any null/undefined values\n          .sort()\n          .map(status => ({ value: status, label: status }));\n\n        return [{ value: 'All', label: 'All Statuses' }, ...uniqueStatuses];\n      })\n    }),\n\n    // Generate unique category options from API data\n    categoryOptionsVar: StateVar({\n      defaultValue: computed(() => {\n        if (!getProductsApi.response) return [{ value: 'All', label: 'All Categories' }];\n\n        const uniqueCategories = [...new Set(getProductsApi.response.map(product => product.category))]\n          .filter(category => category) // Remove any null/undefined values\n          .sort()\n          .map(category => ({ value: category, label: category }));\n\n        return [{ value: 'All', label: 'All Categories' }, ...uniqueCategories];\n      })\n    }),\n\n    // Filtered data based on both dropdowns\n    filteredProductsVar: StateVar({\n      defaultValue: computed(() => {\n        return getProductsApi.response?.filter(product => {\n          const matchesStatus = StatusFilterDropdown.selectedOptionValue === 'All' ||\n            product.status === StatusFilterDropdown.selectedOptionValue;\n          const matchesCategory = CategoryFilterDropdown.selectedOptionValue === 'All' ||\n            product.category === CategoryFilterDropdown.selectedOptionValue;\n          return matchesStatus && matchesCategory;\n        }) || [];\n      })\n    }),\n  }),\n  { name: \"Page1\" }\n);\n\n// In the component, destructure and use\nconst { StatusFilterDropdown, CategoryFilterDropdown, statusOptionsVar, categoryOptionsVar, filteredProductsVar } = Page1;\n\n// Dropdowns with dynamic options from API data\n<Dropdown\n  bind={StatusFilterDropdown}\n  options={computed(() => statusOptionsVar.value)}\n  defaultValue=\"All\"\n/>\n\n<Dropdown\n  bind={CategoryFilterDropdown}\n  options={computed(() => categoryOptionsVar.value)}\n  defaultValue=\"All\"\n/>\n\n// Table showing filtered results\n<Table tableData={computed(() => filteredProductsVar.value)} />\n```\n\n**Key points:**\n\n- Always include an \"All\" option as the first option\n- Use `new Set()` to get unique values from the API response\n- Filter out null/undefined values to avoid empty options\n- Sort the options alphabetically for better UX\n- The dropdown options are reactive - they update when the API data changes\n- Use `bind` properties on dropdowns so that the bind entities you set up in the scope file update automatically when the dropdown values change\n- Default to \"All\" to show all data initially\n";
 //# sourceMappingURL=superblocks-data-filtering.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-event-flow.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-event-flow.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.042Z
+// Generated at: 2025-10-09T14:20:12.229Z
 export const content = "# Event handlers with EventFlow\n\nRather than using standard browser event handlers, Superblocks provides a structured event handler action flow that allows you to run a series of events within the Superblocks system.\n\nImporting EventFlow:\n\n```jsx\nimport { EventFlow } from \"@superblocksteam/library\";\n```\n\nAll event handlers MUST be written using the `EventFlow` object.\n\nFor example, here we set the `isReady` state variable to `true` when the button is clicked:\n\n```jsx\nconst { isReady } = Page1;\n<Button onClick={EventFlow.setStateVar(isReady, { value: true })} />;\n```\n\n## EventFlow builder pattern\n\n`EventFlow` provides a number of functions that can be chained together using `EventFlow` which correspond to actions in the Superblocks system.\n\nYou should always use these dedicated functions for individual and sequential actions.\n\nImportant: DO NOT use .run() at the end of a chain of EventFlow functions, it is not needed and it will throw an error.\n\n```jsx\nconst { isReady, getUserData, getPermissions, LoginModal } = Page1;\n<Button\n  onClick={EventFlow.setQueryParams({ filter: \"active\" }, { keep: true })\n    .setStateVar(isReady, { value: true })\n    .controlModal(LoginModal, { action: \"close\" })\n\n    // run APIs allows you to run Superblocks APIs by name using string arrays\n    // Each runAPIs call executes the list of API names supplied in parallel\n    .runApis([getUserData, getPermissions])\n\n    // set a state variable's value\n    .showAlert(\"Workflow complete\", { type: \"success\" })\n    .navigateTo(\"/dashboard\", { newWindow: false })}\n/>;\n```\n\n#### Using RunJS (only when needed)\n\n`EventFlow` also has a special `runJS` event type that allows you to run any JavaScript in the browser.\n\nThis allows you to write more complex logic such as control flow.\n\nImportant:\n\n- The only things you can do in runJS is set state variables or set the public state of components, like modal.isOpen.\n- You CANNOT use EventFlow inside of a EventFlow.runJS function. If you do this, it won't work!\n- **State access in runJS**: Scope entities are accessible directly by their names, global state is accessible via imported globals (Global, Theme, Embed, Env).\n\nExample accessing scope entities:\n\n```jsx\n<Button\n  label=\"Enable\"\n  buttonStyle={\"SECONDARY_BUTTON\"}\n  onClick={EventFlow.runJS(() => {\n    // Scope entities (variables, bound components) are accessible directly in runJS\n    if (isUserAdmin.value) {\n      // isUserAdmin is a bound component from scope\n      myStateVar.value = true; // myStateVar is a state variable from scope\n      myModal.isOpen = false; // myModal is a bound component from scope\n    } else {\n      console.log(\"This user was not an admin\");\n    }\n  })}\n/>\n```\n\nExample accessing global state when needed:\n\n```jsx\n<Button\n  label=\"Personalized Action\"\n  onClick={EventFlow.runJS(() => {\n    // Import globals and access directly\n    if (Global.user?.groups.some((g) => g.name === \"admin\")) {\n      // Also access scope entities (bound components) directly\n      adminPanel.isVisible = true; // adminPanel is a bound component from scope\n    }\n    console.log(`Welcome ${Global.user?.name}!`);\n  })}\n/>\n```\n\nAs mentioned above, you should only use `runJS` when the flow is too complex to represent using only chained event flow actions.\n\n### EventFlow Usage Examples\n\n```typescript\nimport { EventFlow, computed } from \"@superblocksteam/library\";\nimport { Page1 } from \"./scope\";\n\nconst { fetchUserData, saveUserData, userDataVariable, MyModal } = Page1;\n\n// Navigation example\nEventFlow.navigateTo(\"https://example.com\", { newWindow: true });\n\n// Control UI components example\nEventFlow.controlModal(MyModal, { action: \"open\" });\n\n// State management example\nconst { userProfile } = Page1;\nEventFlow.setStateVar(userProfile, { value: { name: \"John\", role: \"Admin\" } });\n\n// Chaining multiple actions\nEventFlow.runApis([fetchUserData])\n  .setStateVar(userDataVariable, {\n    value: computed(() => {\n      fetchUserData.response;\n    }),\n  })\n  .showAlert(\"Data loaded successfully\", { type: \"success\" });\n\n// Conditional flow with success/error handlers\nconst successFlow = EventFlow.showAlert(\"Success!\", { type: \"success\" });\nconst errorFlow = EventFlow.showAlert(\"An error occurred\", { type: \"error\" });\nEventFlow.runApis([saveUserData], {\n  onSuccess: successFlow,\n  onError: errorFlow,\n});\n```\n\n**EventFlow: Managing Events and Side Effects in Superblocks**\n\n## Important Syntax Rules\n\n- Always use function braces with EventFlow.runJS. Example: `EventFlow.runJS(() => { someFunction(); })` not `EventFlow.runJS(() => someFunction())`\n- EventFlow.runApis() accepts an array of direct API entity references. Example: `EventFlow.runApis([fetchUserData, saveUserData])`\n";
 //# sourceMappingURL=superblocks-event-flow.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-forms.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-forms.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.042Z
+// Generated at: 2025-10-09T14:20:12.228Z
 export const content = "### Form Layouts in Superblocks\n\n**🚨 CRITICAL: Remember that computed cannot be used as React children.** When building forms, all dynamic content must be in component properties (like `text={}`, `label={}`) not as children.\n\nWhen creating forms using form field components, follow these rules:\n\n1. Always put form components together inside an `Container` with `layout=\"vertical\"`, `width={Dim.fill()}`, and appropriate `spacing`\n2. Use `spacing={Dim.px(12)}` or similar for consistent form field spacing\n3. Do not change the label position on form components (like `Input`). The default is the label is above the input and we want to keep that\n4. Make all form field components and any container parents be `width={Dim.fill()}` so they are all aligned horizontally and easy to use\n\n**Example:**\n\n```jsx\n<Container layout=\"vertical\" width={Dim.fill()} spacing={Dim.px(12)}>\n  <Input label=\"First Name\" bind={FirstName} width={Dim.fill()} />\n  <Input label=\"Last Name\" bind={LastName} width={Dim.fill()} />\n  <Input label=\"Email\" bind={Email} inputType=\"EMAIL\" width={Dim.fill()} />\n</Container>\n```\n\n### Forms inside Modals\n\nIt's common to put a form inside a Modal, like for creating or editing an entity. Here are comprehensive examples showing different patterns:\n\n#### Basic Create Form Modal\n\n```tsx\n// Import required components and utilities\nimport {\n  Modal,\n  Container,\n  Text,\n  Input,\n  Dropdown,\n  Button,\n  Dim,\n  EventFlow,\n} from \"@superblocksteam/library\";\nimport { Page1 } from \"./scope\";\n\n// ...\n\nconst {\n  NewOrderCustomerName,\n  NewOrderCustomerEmail,\n  NewOrderAmount,\n  NewOrderStatus,\n  NewOrderNotes,\n  OrdersStateVar,\n  CreateOrderModal,\n} = Page1;\n\n<Modal bind={CreateOrderModal}>\n  <Container layout=\"vertical\" width={Dim.fill()} spacing={Dim.px(24)}>\n    {/* Modal Header */}\n    <Container layout=\"vertical\" spacing={Dim.px(8)}>\n      <Text\n        text=\"Create New Order\"\n        textStyle={{\n          variant: \"heading4\",\n        }}\n      />\n      <Text text=\"Fill out the form below to create a new order\" />\n    </Container>\n\n    {/* Form Content */}\n    <Container layout=\"vertical\" width={Dim.fill()} spacing={Dim.px(12)}>\n      <Input\n        bind={NewOrderCustomerName}\n        width={Dim.fill()}\n        label=\"Customer Name\"\n        placeholderText=\"Enter customer name\"\n        required={true}\n      />\n\n      <Input\n        bind={NewOrderCustomerEmail}\n        width={Dim.fill()}\n        label=\"Customer Email\"\n        inputType=\"EMAIL\"\n        placeholderText=\"Enter customer email\"\n        required={true}\n      />\n\n      <Input\n        bind={NewOrderAmount}\n        width={Dim.fill()}\n        label=\"Order Amount\"\n        placeholderText=\"Enter order amount\"\n        inputType=\"NUMBER\"\n        required={true}\n      />\n\n      <Dropdown\n        bind={NewOrderStatus}\n        width={Dim.fill()}\n        label=\"Order Status\"\n        options={[\n          {\n            label: \"Pending\",\n            value: \"pending\",\n          },\n          {\n            label: \"Processing\",\n            value: \"processing\",\n          },\n          {\n            label: \"En route\",\n            value: \"en_route\",\n          },\n          {\n            label: \"Delivered\",\n            value: \"delivered\",\n          },\n          {\n            label: \"Refunded\",\n            value: \"refunded\",\n          },\n        ]}\n        required={true}\n      />\n\n      <Input\n        bind={NewOrderNotes}\n        width={Dim.fill()}\n        label=\"Order Notes\"\n        placeholderText=\"Optional notes about the order\"\n        multiline={true}\n      />\n    </Container>\n\n    {/* Modal Footer */}\n    <Container\n      layout=\"horizontal\"\n      horizontalAlign=\"right\"\n      spacing={Dim.px(12)}\n      width={Dim.fill()}\n    >\n      <Button\n        label=\"Cancel\"\n        variant=\"secondary\"\n        onClick={EventFlow.runJS(() => {\n          // Reset form components\n          NewOrderCustomerName.text = \"\";\n          NewOrderCustomerEmail.text = \"\";\n          NewOrderAmount.text = \"\";\n          NewOrderStatus.value = \"\";\n          NewOrderNotes.text = \"\";\n        })\n          // Note how we prefer use controlModal for handling opening/closing\n          // the modal rather than setting the modal's open property directly\n          .controlModal(CreateOrderModal, { action: \"close\" })}\n      />\n      <Button\n        label=\"Create Order\"\n        variant=\"primary\"\n        onClick={EventFlow.runJS(() => {\n          // Create new order using the form values\n          const newOrder = {\n            id: `ORD_${Math.floor(Math.random() * 10000)\n              .toString()\n              .padStart(4, \"0\")}`,\n            customerName: NewOrderCustomerName.value,\n            customerEmail: NewOrderCustomerEmail.value,\n            amount: NewOrderAmount.value,\n            status: NewOrderStatus.selectedOptionValue,\n            notes: NewOrderNotes.value,\n            createdAt: new Date().toISOString(),\n          };\n\n          // Add to orders list or call API\n          OrdersStateVar.setValue([...OrdersStateVar.value, newOrder]);\n\n          // Reset form components\n          NewOrderCustomerName.text = \"\";\n          NewOrderCustomerEmail.text = \"\";\n          NewOrderAmount.text = \"\";\n          NewOrderStatus.value = \"\";\n          NewOrderNotes.text = \"\";\n        })\n          // Note how we prefer use controlModal for handling opening/closing\n          // the modal rather than setting the modal's open property directly\n          .controlModal(CreateOrderModal, { action: \"close\" })}\n      />\n    </Container>\n  </Container>\n</Modal>;\n```\n\n#### Table with Edit Form Modal\n\nThis example shows a more complete pattern where a table displays data and clicking a row opens an edit modal with the form fields pre-populated:\n\n```tsx\n// Import required components and utilities\nimport {\n  Page,\n  Container,\n  Table,\n  Modal,\n  Container,\n  Text,\n  Input,\n  Dropdown,\n  Button,\n  Dim,\n  EventFlow,\n  computed,\n} from \"@superblocksteam/library\";\nimport { Page1 } from \"./scope\";\n\nconst {\n  OrdersTable,\n  EditOrderModal,\n  EditOrderCustomerName,\n  EditOrderCustomerEmail,\n  EditOrderAmount,\n  EditOrderStatus,\n  EditOrderNotes,\n  OrdersStateVar,\n} = Page1;\n\n// Main page with table\n<Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n  <Container height={Dim.fill()} width={Dim.fill()} spacing={Dim.px(24)}>\n    <Text\n      text=\"Orders Management\"\n      textStyle={{ variant: \"heading2\" }}\n    />\n\n    <Table\n      bind={OrdersTable}\n      tableData={computed(() => OrdersStateVar.value)}\n      onRowClick={EventFlow.runJS(() => {\n        // Populate form fields with the selected row data\n        EditOrderCustomerName.text = OrdersTable.selectedRow.customerName;\n        EditOrderCustomerEmail.text = OrdersTable.selectedRow.customerEmail;\n        EditOrderAmount.text = OrdersTable.selectedRow.amount;\n        EditOrderStatus.value = OrdersTable.selectedRow.status;\n        EditOrderNotes.text = OrdersTable.selectedRow.notes || \"\";\n      })\n        // Open the edit modal\n        .controlModal(EditOrderModal, { action: \"open\" })}\n      width={Dim.fill()}\n      height={Dim.fill()}\n    />\n  </Container>\n</Page>\n\n// Edit modal with form pre-populated from table row\n<Modal bind={EditOrderModal}>\n  <Container layout=\"vertical\" width={Dim.fill()} spacing={Dim.px(24)}>\n    {/* Modal Header */}\n    <Container layout=\"vertical\" spacing={Dim.px(8)}>\n      <Text\n        text=\"Edit Order\"\n        textStyle={{\n          variant: \"heading4\",\n        }}\n      />\n      <Text text=\"Update the order details below\" />\n    </Container>\n\n    {/* Form Content - Fields are pre-populated by onRowClick */}\n    <Container layout=\"vertical\" width={Dim.fill()} spacing={Dim.px(12)}>\n      <Input\n        bind={EditOrderCustomerName}\n        width={Dim.fill()}\n        label=\"Customer Name\"\n        placeholderText=\"Enter customer name\"\n        required={true}\n      />\n\n      <Input\n        bind={EditOrderCustomerEmail}\n        width={Dim.fill()}\n        label=\"Customer Email\"\n        inputType=\"EMAIL\"\n        placeholderText=\"Enter customer email\"\n        required={true}\n      />\n\n      <Input\n        bind={EditOrderAmount}\n        width={Dim.fill()}\n        label=\"Order Amount\"\n        placeholderText=\"Enter order amount\"\n        inputType=\"NUMBER\"\n        required={true}\n      />\n\n      <Dropdown\n        bind={EditOrderStatus}\n        width={Dim.fill()}\n        label=\"Order Status\"\n        options={[\n          {\n            label: \"Pending\",\n            value: \"pending\",\n          },\n          {\n            label: \"Processing\",\n            value: \"processing\",\n          },\n          {\n            label: \"En route\",\n            value: \"en_route\",\n          },\n          {\n            label: \"Delivered\",\n            value: \"delivered\",\n          },\n          {\n            label: \"Refunded\",\n            value: \"refunded\",\n          },\n        ]}\n        required={true}\n      />\n\n      <Input\n        bind={EditOrderNotes}\n        width={Dim.fill()}\n        label=\"Order Notes\"\n        placeholderText=\"Optional notes about the order\"\n        multiline={true}\n      />\n    </Container>\n\n    {/* Modal Footer */}\n    <Container\n      layout=\"horizontal\"\n      horizontalAlign=\"right\"\n      spacing={Dim.px(12)}\n      width={Dim.fill()}\n    >\n      <Button\n        label=\"Cancel\"\n        variant=\"secondary\"\n        onClick={EventFlow.controlModal(EditOrderModal, { action: \"close\" })}\n      />\n      <Button\n        label=\"Save Changes\"\n        variant=\"primary\"\n        onClick={EventFlow.runJS(() => {\n          // Find and update the order in the orders array\n          const updatedOrders = OrdersStateVar.value.map(order => {\n            if (order.id === OrdersTable.selectedRow.id) {\n              return {\n                ...order,\n                customerName: EditOrderCustomerName.value,\n                customerEmail: EditOrderCustomerEmail.value,\n                amount: EditOrderAmount.value,\n                status: EditOrderStatus.selectedOptionValue,\n                notes: EditOrderNotes.value,\n                updatedAt: new Date().toISOString(),\n              };\n            }\n            return order;\n          });\n\n          // Update the orders state\n          OrdersStateVar.setValue(updatedOrders);\n        })\n          .controlModal(EditOrderModal, { action: \"close\" })}\n      />\n    </Container>\n  </Container>\n</Modal>\n```\n\n**Corresponding scope.ts file for the table + edit modal example:**\n\n```ts\n// pages/Page1/scope.ts\nimport {\n  createScope,\n  StateVar,\n  StateVarPersistence,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  OrdersTable: any;\n  EditOrderModal: any;\n  EditOrderCustomerName: any;\n  EditOrderCustomerEmail: any;\n  EditOrderAmount: any;\n  EditOrderStatus: any;\n  EditOrderNotes: any;\n  OrdersStateVar: any;\n}>(\n  () => ({\n    OrdersStateVar: StateVar({\n      defaultValue: [\n        {\n          id: 1,\n          customerName: \"John Doe\",\n          customerEmail: \"john@example.com\",\n          amount: 150.0,\n          status: \"pending\",\n          notes: \"Rush order\",\n          createdAt: \"2024-01-15T10:30:00Z\",\n        },\n        {\n          id: 2,\n          customerName: \"Jane Smith\",\n          customerEmail: \"jane@example.com\",\n          amount: 89.99,\n          status: \"delivered\",\n          notes: \"\",\n          createdAt: \"2024-01-14T14:20:00Z\",\n        },\n      ],\n      persistence: StateVarPersistence.TEMPORARY,\n    }),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n#### Alternative Population Method - Button with State Variable\n\nHere's another common pattern where a button populates form fields from a state variable:\n\n```tsx\n// Button that loads selected user data into edit form\n<Button\n  label=\"Edit Selected User\"\n  onClick={EventFlow.runJS(() => {\n    const selectedUser = SelectedUserStateVar.value;\n\n    // Populate form fields from state variable\n    EditUserName.text = selectedUser.name;\n    EditUserEmail.text = selectedUser.email;\n    EditUserRole.value = selectedUser.role;\n    EditUserDepartment.text = selectedUser.department;\n  }).controlModal(EditUserModal, { action: \"open\" })}\n/>\n```\n\n### Key Form Patterns\n\n1. **Create Forms**: Start with empty fields, populate from user input\n2. **Edit Forms**: Pre-populate fields with existing data from various sources\n3. **Field Population Methods**:\n   - **Table Row Selection**: Use `onRowClick` to set form field values to `{TableName}.selectedRow.{columnName}` (most common)\n   - **Button Actions**: Use button clicks to populate from state variables or API responses\n   - **API Loading**: Fetch data and populate fields when modal opens\n   - **State Variables**: Populate from existing application state\n4. **Form Validation**: Use `required={true}` on form components and validate in submit handlers\n5. **Form Reset**: Always reset form fields when canceling or after successful submission\n6. **Modal Control**: Prefer `EventFlow.controlModal()` over directly setting modal open property\n\n### Form Layout Best Practices\n\n- **Container Structure**: Always wrap forms in `Container` with `layout=\"vertical\"`\n- **Consistent Spacing**: Use `spacing={Dim.px(12)}` for form field spacing\n- **Full Width**: Make form fields and containers `width={Dim.fill()}` for proper alignment\n- **Modal Structure**: Use header, content, and footer containers with appropriate spacing\n- **Button Alignment**: Use `horizontalAlign=\"right\"` for the footer containers in modals that contain buttons\n";
 //# sourceMappingURL=superblocks-forms.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-layouts.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-layouts.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.042Z
+// Generated at: 2025-10-09T14:20:12.228Z
 export const content = "### Layout and Sizing in Superblocks\n\n**Container Component:**\n\n```jsx\n<Container\n  variant=\"card\" | \"none\" // default: \"none\" (pure layout) vs \"card\" (visual styling)\n  layout=\"vertical\" | \"horizontal\" | \"freeform\" // default: \"vertical\", prefer vertical/horizontal\n>\n  {/* Children */}\n</Container>\n```\n\n**Sizing with Dim:**\n\n- `Dim.fit()` - Fit to content (default, can be omitted)\n- `Dim.px(100)` - Fixed pixel size\n- `Dim.fill()` or `Dim.fill(2)` - Fill available space with optional weight\n\n**Sizing Guidelines:** Prefer `Dim.fill()` and `Dim.fit()` over `Dim.px()` for responsive layouts.\n\n**Standard Page Structure:**\n\n```tsx\n<Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n  <Container height={Dim.fill()} width={Dim.fill()}>\n    {/* Page content */}\n  </Container>\n</Page>\n```\n\n**Container Width Rule:** Use `width={Dim.fill()}` for containers under Page, and for modal/slideout roots.\n\n**Sidebar Layout Example:**\n\n```tsx\n<Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n  <Container height={Dim.fill()} layout=\"horizontal\">\n    <Container width={Dim.px(250)}>{/* Fixed sidebar */}</Container>\n    <Container width={Dim.fill()}>{/* Flexible content */}</Container>\n  </Container>\n</Page>\n```\n\n**Modal Layout:**\n\n- Root container: `<Container layout=\"vertical\" width={Dim.fill()}>`\n- Modal includes default close button\n- Header/footer in separate containers; footer buttons use `horizontalAlign=\"right\"`\n- Most components use `width={Dim.fill()}` except buttons (use default `Dim.fit()`)\n";
 //# sourceMappingURL=superblocks-layouts.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-page.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-page.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.228Z
 export const content = "### How to use Page\n\n**Important: Superblocks apps currently support only one page.**\n\n- A Superblocks app consists of a single page that exports a default React component through the `registerPage` function.\n- The page consists of two files: `index.tsx` (the page component) and `scope.ts` (the entity definitions).\n- For `export default registerPage(Page1, Page1Scope)`, Page1 is a function that returns a React component, and Page1Scope is the scope containing all entities.\n- A Superblocks app consists of a single page located in the `pages/Page1` directory.\n- NEVER change the path of the `pages` directory or the page directories inside it `like `pages/Page1`). If you change these paths or folder names, the app will crash.\n- DO NOT create more than ONE page in an app. Multiple pages is NOT supported!\n\n### Page Structure\n\nThe single page in your Superblocks app should have the following structure:\n\n**scope.ts** - Contains all entity definitions (variables, APIs, etc.):\n\n```ts\nimport Text from \"components/ui/Text/index\";\nimport {\n  createScope,\n  StateVar,\n  StateVarPersistence,\n  SbApi,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  Text1: any;\n}>(\n  () => ({\n    // Define your entities here\n    myVariableVar: StateVar({\n      defaultValue: \"initial value\",\n      persistence: StateVarPersistence.TEMPORARY,\n    }),\n    fetchDataApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n**index.tsx** - Contains the page component:\n\n```tsx\nimport Container from \"components/ui/Container/index\";\nimport Text from \"components/ui/Text/index\";\nimport { Page, registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nfunction PageContent() {\n  // Destructure entities from the scope for easy access\n  const { Text1, myVariableVar, fetchDataApi } = Page1;\n\n  return (\n    <Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        {/* Use entities in your components */}\n        <Text bind={Text1} text={computed(() => myVariableVar.value)} />\n      </Container>\n    </Page>\n  );\n}\n\nexport default registerPage(PageContent, Page1Scope);\n```\n\n## How component bindings work\n\nIf you need to reference a component directly to get access to some of its state, you must use a binding inside the page scope.\n\nComponent bindings allow you to:\n\n- Access component properties and state from other components and APIs\n- Create reactive relationships between components\n- Reference component values in `computed` expressions\n\n### Setting up component bindings\n\n1. **Define the binding type in your scope**: Add the component type to the scope's type definitions:\n\n```ts\nexport const Page1Scope = createScope<{\n  Text1: any;\n  UserInput: any;\n}>(\n  () => ({\n    // Your other entities (variables, APIs, etc.)\n    myVariableVar: StateVar({ defaultValue: \"Hello\" }),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n2. **Bind the component in your JSX**: Use the `bind` prop to connect the component to the binding:\n\n```tsx\nfunction PageContent() {\n  const { Text1, UserInput, myVariableVar } = Page1;\n\n  return (\n    <Page name=\"Page1\" height={Dim.fill()} width={Dim.fill()}>\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        <Input bind={UserInput} placeholder=\"Enter your name\" />\n        <Text\n          bind={Text1}\n          text={computed(() => `Hello, ${UserInput.value}!`)}\n        />\n      </Container>\n    </Page>\n  );\n}\n```\n\n3. **Access component state**: Use `computed` to access properties of bound components:\n\n```tsx\n// Access input value\ntext={computed(() => UserInput.value)}\n\n// Access text content\ntext={computed(() => Text1.text)}\n\n// Combine with other state\n            text={computed(() => `${myVariableVar.value}: ${UserInput.value}`)}\n```\n\n### Common binding use cases\n\n- **Form inputs**: Access user input values to display or validate\n- **Dynamic content**: Reference one component's state to update another\n- **Conditional rendering**: Use component state to control visibility or styling\n\n### Page load events\n\nYou can fire callbacks when the page is loaded using the onLoad property of the Page component. You must use the EventFlow API for any actions you want to run inside onLoad.\n\nExample:\n\n```tsx\nimport Container from \"components/ui/Container/index\";\nimport {\n  registerPage,\n  EventFlow,\n  Page,\n  computed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return (\n    <Page\n      name=\"Page1\"\n      height={Dim.fill()}\n      width={Dim.fill()}\n      onLoad={EventFlow.runJS(() => {\n        console.log(\"Page loaded\");\n      })}\n    >\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        ...\n      </Container>\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nA very common and helpful usage of this callback is to run APIs using EventFlow to fetch data when the page loads. Example:\n\n```tsx\nimport Container from \"components/ui/Container/index\";\nimport {\n  Page,\n  registerPage,\n  EventFlow,\n  computed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return (\n    <Page\n      name=\"Page1\"\n      height={Dim.fill()}\n      width={Dim.fill()}\n      onLoad={EventFlow.runApis([getOrdersApi])}\n    >\n      <Container height={Dim.fill()} width={Dim.fill()}>\n        ...\n      </Container>\n    </Page>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nIn this example, the `getOrdersApi` API would be defined in the scope.ts file like this:\n\n```ts\n// In scope.ts\n\n// We register the api in createScope by creating a key\n// with the same name as the file, and SbApi({}) with an empty object\n// Note: We DO NOT import the api file. It's not necessary.\nexport const Page1Scope = createScope(\n  () => ({\n    getOrdersApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n";
 //# sourceMappingURL=superblocks-page.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-rbac.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-rbac.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "# Role-Based Access Control (RBAC)\n\nSuperblocks provides role-based access control through user groups. You can control component visibility and availability based on the groups that a user belongs to.\n\n## Accessing User Groups\n\nUser groups are available via `Global.user?.groups`, which contains an array of group objects with the following structure:\n\n```typescript\n// Global.user?.groups is an ARRAY OF OBJECTS, not an array of strings\nGlobal.user?.groups: Array<{\n  id: string;\n  name: string;\n}>;\n\n// Example data:\n// [\n//   { id: \"123\", name: \"Admins\" },\n//   { id: \"456\", name: \"Managers\" },\n//   { id: \"789\", name: \"Order Management Admins\" }\n// ]\n```\n\n## Common RBAC Patterns\n\n### Hiding Components Based on User Groups\n\nThe most common way to implement RBAC is by controlling component visibility using the `isVisible` property. Nearly all components support this property.\n\n```javascript\n// Show a component only to users in the \"Admins\" group\n<Button\n  text=\"Admin Action\"\n  isVisible={Global.user?.groups.some((g) => g.name === \"Admins\")}\n/>\n\n// Show a component only to users NOT in the \"Guest\" group\n<Container\n  isVisible={!Global.user?.groups.some((g) => g.name === \"Guest\")}\n>\n  {/* Content only visible to non-guests */}\n</Container>\n\n// Show a component to users in multiple groups\n<Text\n  text=\"Manager or Admin content\"\n  isVisible={Global.user?.groups.some((g) => [\"Managers\", \"Admins\"].includes(g.name))}\n/>\n```\n\n### Disabling Components Based on User Groups\n\nFor interactive components that support the `isDisabled` property (like buttons, inputs, dropdowns, etc.), you can disable functionality while keeping the component visible:\n\n```javascript\n// Disable a button for users not in the \"Editors\" group\n<Button\n  text=\"Edit Record\"\n  isDisabled={!Global.user?.groups.some((g) => g.name === \"Editors\")}\n/>\n\n// Disable an input for read-only users\n<Input\n  label=\"Sensitive Data\"\n  defaultValue=\"Some value\"\n  isDisabled={Global.user?.groups.some((g) => g.name === \"ReadOnly\")}\n/>\n\n// Enable advanced features only for premium users\n<Dropdown\n  label=\"Advanced Options\"\n  isDisabled={!Global.user?.groups.some((g) => g.name === \"Premium\")}\n/>\n```\n\n## Components with RBAC Support\n\n### Components Supporting `isVisible`\n\nAlmost all components support the `isVisible` property, including:\n\n- Button, Text, Input, Dropdown, Container, Image, Icon, Table, Checkbox, Switch, DatePicker, Modal, Slideout, and more.\n\n### Components Supporting `isDisabled`\n\nInteractive components that support the `isDisabled` property include:\n\n- Button, Input, Dropdown, Checkbox, Switch, DatePicker, and other form controls.\n\n## Best Practices\n\n1. **Use `isVisible` for sensitive content**: Hide components that contain sensitive information or actions that users shouldn't see.\n\n2. **Use `isDisabled` for better UX**: When you want users to see that a feature exists but is not available to them, disable the component rather than hiding it.\n\n3. **Group-based logic**: Use group names consistently across your application for easier maintenance.\n\n4. **Fallback handling**: Consider what happens when a user has no groups or unexpected group configurations.\n\n5. **Test thoroughly**: Always test RBAC logic with users from different groups to ensure proper access control.\n\n## Example: Complete RBAC Implementation\n\n```javascript\n// A dashboard with different access levels\n<Container layout=\"vertical\">\n  {/* Everyone can see this */}\n  <Text text=\"Welcome to the Dashboard\" />\n\n  {/* Only visible to authenticated users (not guests) */}\n  <Button\n    text=\"My Profile\"\n    isVisible={!Global.user?.groups.some((g) => g.name === \"Guest\")}\n  />\n\n  {/* Visible to managers and admins, but disabled for managers */}\n  <Button\n    text=\"Delete Records\"\n    isVisible={Global.user?.groups.some((g) =>\n      [\"Managers\", \"Admins\"].includes(g.name),\n    )}\n    isDisabled={\n      Global.user?.groups.some((g) => g.name === \"Managers\") &&\n      !Global.user?.groups.some((g) => g.name === \"Admins\")\n    }\n  />\n\n  {/* Admin-only section */}\n  <Container isVisible={Global.user?.groups.some((g) => g.name === \"Admins\")}>\n    <Text text=\"Admin Controls\" />\n    <Button text=\"System Settings\" />\n    <Button text=\"User Management\" />\n  </Container>\n</Container>\n```\n";
 //# sourceMappingURL=superblocks-rbac.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-routes.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-routes.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "- **IMPORTANT: Superblocks apps support only ONE page. There is only ever a single route mapping to the single page.**\n- The `routes.json` file maps the root URL to the single page in your Superblocks app.\n  Example routes.json file content:\n\n```json\n{\n  \"/\": {\n    \"file\": \"Page1/index.tsx\"\n  }\n}\n```\n\nIn the above example, the '/' route maps to the single Page1 in your Superblocks app.\n\n**Critical: Superblocks apps only support a single page, so the routes.json file should only contain one route mapping to Page1.**\n\nCritical: Page paths in `routes.json` are relative to the 'pages/' directory. In this file, you must never prefix `file` values with 'pages/', or the app will break.\n";
 //# sourceMappingURL=superblocks-routes.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-state.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-state.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "# Superblocks State System\n\n## Core Concepts\n\n### Scopes\n\n- Single `scope.ts` file per page defines all entities (state variables, APIs, components)\n- Entities are accessed via destructuring after import\n- Child scopes can access parent entities; parents cannot access children\n\n### Entity Types\n\n#### 1. Component State\n\n- Define component type in scope, use `bind` prop to connect\n- **Each entity name can only bind to ONE component instance** (e.g., if you have 3 Input components, define 3 different entities: SearchInput, NameInput, EmailInput)\n- Access via `computed(() => ComponentName.prop)`\n- Components requiring bindings: Input, Dropdown, DatePicker, Checkbox, Switch, Form, Radio, RichText, FilePicker, CodeEditorEditor, Chat\n\n#### 2. State Variables\n\n- Static: `StateVar({ defaultValue: \"value\" })`\n- Computed initial value: Wrap scope in `({ entities }) => ({ ... })` and use `computed(() => ...)`\n- Read: `computed(() => varName.value)` - always include `.value`\n- Write: `EventFlow.setStateVar(varName, { value: newValue })` or within `EventFlow.runJS(() => { varName.value = newValue; })`\n- **Cannot store functions** - only JSON-serializable data\n\n#### 3. APIs\n\n- Define: `SbApi({})` in scope\n- Read: `computed(() => apiName.response)` or `computed(() => apiName.error)`\n- Read-only\n\n## Access Patterns\n\n### Scope Entities (Direct Access)\n\n```tsx\nconst { UserInput, myVar, dataApi } = Page1;\n<Text text={computed(() => UserInput.value)} />\n<Table tableData={computed(() => dataApi.response)} />\n```\n\n### Global State (Import Access)\n\n```tsx\n// Import globals from library\n<Text text={computed(() => `Welcome ${Global.user?.name}!`)} />\n<Container backgroundColor={computed(() => Theme.colors.primary)} />\n```\n\n## Critical Rules\n\n1. **Never create redundant state** - Use component state directly via bindings\n2. **Unique names only** - All entities in createScope must have unique names\n3. **One binding per entity** - Each component entity (e.g., CustomerSearchInput) can ONLY bind to ONE component instance. Need multiple inputs? Define CustomerSearchInput, CustomerNameInput, CustomerEmailInput, etc.\n4. **No function storage** - State variables cannot store or be used as functions\n5. **Complete implementation** - Never stub or skip features\n\n## Example: Complete Page with Scope\n\n```ts\n// pages/Page1/scope.ts\nimport {\n  createScope,\n  StateVar,\n  StateVarPersistence,\n  SbApi,\n  computed,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createScope<{\n  SearchInput: any;\n  StatusDropdown: any;\n}>(\n  ({ entities: { SearchInput } }) => ({\n    // Component bindings defined in type parameter above\n\n    // Static state\n    ordersVar: StateVar({\n      defaultValue: [],\n      persistence: StateVarPersistence.TEMPORARY,\n    }),\n\n    // Computed initial value from component\n    searchTermVar: StateVar({\n      defaultValue: computed(() => SearchInput.value || \"\"),\n      persistence: StateVarPersistence.TEMPORARY,\n    }),\n\n    // API\n    fetchOrdersApi: SbApi({}),\n  }),\n  { name: \"Page1\" },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n```tsx\n// pages/Page1/index.tsx\nimport {\n  Page,\n  computed,\n  EventFlow,\n  registerPage,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nfunction PageContent() {\n  const { SearchInput, StatusDropdown, ordersVar, fetchOrdersApi } = Page1;\n\n  return (\n    <Page name=\"Page1\">\n      <Input bind={SearchInput} placeholder=\"Search orders...\" />\n\n      <Dropdown\n        bind={StatusDropdown}\n        options={[\n          { label: \"Active\", value: \"active\" },\n          { label: \"Completed\", value: \"completed\" },\n        ]}\n      />\n\n      <Table\n        tableData={computed(() =>\n          ordersVar.value.filter(\n            (order) =>\n              order.name.includes(SearchInput.value) &&\n              order.status === StatusDropdown.selectedOptionValue,\n          ),\n        )}\n      />\n\n      <Button text=\"Refresh\" onClick={EventFlow.runAPI(fetchOrdersApi)} />\n    </Page>\n  );\n}\n\nexport default registerPage(PageContent, Page1Scope);\n```\n\n## Common Mistakes to Avoid\n\n❌ **Creating redundant state variables for component values**\n\n```tsx\n// WRONG\n<Input\n  bind={UserInput}\n  onChange={EventFlow.setStateVar(userVar, { value: \"val\" })}\n/>\n```\n\n❌ **Using state variables as functions**\n\n```tsx\n// WRONG\nfilterOrders: StateVar({\n  defaultValue: () => {\n    /* function */\n  },\n});\n```\n\n❌ **Reusing component entity names**\n\n```tsx\n// WRONG - Can't use Input1 for multiple inputs\n<Input bind={Input1} />\n<Input bind={Input1} /> // Error!\n```\n\n✅ **Correct approach**\n\n```tsx\n// Define separate entities for each component\n<Input bind={FirstNameInput} />\n<Input bind={LastNameInput} />\n<Text text={computed(() => `${FirstNameInput.value} ${LastNameInput.value}`)} />\n```\n";
 //# sourceMappingURL=superblocks-state.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/superblocks-theming-chakra-new.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from superblocks-theming-chakra-new.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "# Superblocks Chakra UI Theming Guide\n\n## Overview\n\nSuperblocks uses Chakra UI v3 for theming. The theme system prioritizes semantic tokens, color palettes, and recipe variants over direct CSS overrides. This guide provides essential patterns for building themeable components. The theme is defined in `theme.ts` and is a Chakra theme object, you should modify it as necessary if you are making a new app. DO NOT delete information from the theme or edit the theme in unnecessary ways. For example, do not remove border radius information from the theme unless you have a very good reason. Only make edits that are clearly necessary to achieve the user's request.\n\n## Priority Order for Styling\n\n1. **Theme tokens and semantic tokens** (preferred)\n2. **Recipe variants and component recipes**\n3. **Color palette properties**\n4. **CSS overrides** (last resort only)\n\n## Theme File Structure\n\n**IMPORTANT: When modifying theme.ts, DO NOT change the export structure or imports. Only modify the content within the config object.**\n\nThe theme file follows this exact structure:\n\n```tsx\nimport { defaultConfig, ThemingConfig } from \"@chakra-ui/react\";\nimport { inputFieldRecipe } from \"components/ui/Input/recipe\";\n// ... other recipe imports\n\nconst config = {\n  tokens: {\n    /* design tokens */\n  },\n  semanticTokens: {\n    /* semantic tokens */\n  },\n  recipes: {\n    /* component recipes */\n  },\n  slotRecipes: {\n    /* multi-slot component recipes */\n  },\n} satisfies ThemingConfig;\n\nexport default config;\n```\n\n**DO NOT modify:**\n\n- Import statements\n- Export statement (`export default config;`)\n- The `satisfies ThemingConfig` type annotation\n- The basic structure of the config object\n\n## Theme Structure\n\n### 1. Semantic Tokens (Preferred)\n\nDefine semantic color palettes instead of raw colors:\n\n```tsx\nsemanticTokens: {\n  colors: {\n    primary: {\n      solid: { value: \"#27BBFF\" },\n      contrast: { value: \"white\" },\n      fg: { value: \"#1a365d\" },\n      muted: { value: \"#bee3f8\" },\n      subtle: { value: \"#ebf8ff\" },\n      emphasized: { value: \"#90cdf4\" },\n      focusRing: { value: \"#27BBFF\" },\n    },\n    secondary: {\n      solid: { value: \"#333388\" },\n      contrast: { value: \"white\" },\n      // ... other palette tokens\n    }\n  },\n  radii: {\n    component: { value: \"6px\" },\n    container: { value: \"10px\" },\n  },\n  spacing: {\n    ...\n  }\n}\n```\n\n### 2. Component Recipes\n\nOverride or extend component base styles and variants:\n\n```tsx\nrecipes: {\n  button: {\n    base: {\n      borderRadius: \"component\", // Use semantic token\n    },\n    variants: {\n      visual: {\n        custom: {\n          bg: \"primary.solid\",\n          color: \"primary.contrast\",\n          _hover: { bg: \"primary.emphasized\" }\n        }\n      }\n    }\n  }\n}\n```\n\nYou can then use it as a prop on the button component:\n\n```tsx\n<Button visual=\"custom\" />\n```\n\n### 3. Slot Recipes\n\nFor multi-part components, use slot recipes:\n\n```tsx\nslotRecipes: {\n  inputField: {\n    slots: [\"root\", \"label\", \"input\", \"description\"],\n    base: {\n      input: {\n        borderRadius: \"component\",\n      }\n    },\n    variants: {\n      size: {\n        lg: {\n          input: { fontSize: \"lg\" },\n          label: { fontSize: \"lg\" }\n        }\n      }\n    }\n  }\n}\n```\n\nYou can then use it as a prop on the input field component:\n\n```tsx\n<InputField size=\"lg\" />\n```\n\n## Component Implementation Patterns\n\n### Using Color Palettes (Required)\n\nAlways use `colorPalette` prop instead of hardcoded colors:\n\n```tsx\n// ✅ Correct - uses color palette\n<Button colorPalette=\"primary\" variant=\"solid\">\n  Click me\n</Button>\n\n// ❌ Wrong - hardcoded color\n<Button bg=\"blue.500\">\n  Click me\n</Button>\n```\n\n### CSS Overrides (Last Resort)\n\nOnly use CSS overrides when theme tokens cannot achieve the desired result, you should still use tokens in the css prop to achieve the desired result. Anytime you see yourself reaching for `css` quickly decide if you could put this inside the theme file instead, or use an existing variant.\n\n```tsx\n// Only when absolutely necessary\n<Button\n  colorPalette=\"primary\"\n  css={{\n    background: \"linear-gradient(45deg, red, blue)\", // Complex styling\n    borderRadius: \"component\",\n  }}\n>\n  Gradient Button\n</Button>\n```\n\nInstead do this:\n\n`theme.ts` - Add to the existing recipes object:\n\n```tsx\nrecipes: {\n  button: {\n    // ... existing button recipe properties\n    variants: {\n      // ... existing variants\n      visual: {\n        // ... existing visual variants\n        gradient: {\n          background: \"linear-gradient(45deg, red, blue)\",\n          borderRadius: \"component\",\n        }\n      }\n    }\n  }\n}\n```\n\n```tsx\n<Button colorPalette=\"primary\" visual=\"gradient\">\n  Click me\n</Button>\n```\n\n## Available Color Palettes by default, you can add more if you want\n\nDefault semantic color palettes available:\n\n- `primary` - Main brand color\n- `secondary` - Secondary brand color\n- `gray` - Neutral colors\n- `red`, `green`, `blue`, `orange`, `purple`, etc. - Standard color scales\n\nEach palette includes: `solid`, `contrast`, `fg`, `muted`, `subtle`, `emphasized`, `focusRing`\n\n## Best Practices\n\n1. **Always use color palettes** - Set `colorPalette` prop instead of specific colors\n2. **Prefer semantic tokens** - Use `primary.solid` instead of `blue.500`\n3. **Extend recipes in theme.ts** - Add variants to existing recipes rather than CSS overrides\n4. **AVOID CSS OVERRIDES** - These are a last resort, especially for things that are considered \"visual\"\n";
 //# sourceMappingURL=superblocks-theming-chakra-new.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/system-base.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from system-base.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "You are Clark, an expert AI assistant and exceptional senior software developer with vast knowledge of the Superblocks framework.\n\n<system_constraints>\nCore Superblocks Framework Principles:\n\n1. **Framework Architecture**\n   - Superblocks apps are single-page applications (all code goes in pages/Page1/index.tsx)\n   - Custom components belong in the components directory\n   - Core framework files (root.tsx, App.tsx, app.css) must not be modified\n\n2. **Code Organization**\n   - Avoid helper functions - inline code for editability in the visual editor\n   - Destructure Page1 entities at component top\n   - Use `computed()` only for dynamic data references inside component properties (state, API responses, component values). Don't use `computed()` as react children, just reference the data in a normal way\n\n3. **Component Rendering**\n   - Use the `isVisible` property for conditional rendering (not React patterns like `{condition && <Component />}`)\n   - Define component properties inline for visual editor compatibility\n   - Import all needed Superblocks components in the first import statement\n   - When mapping/iterating over arrays to render components, wrap the map result in a `<div>` element (required for proper rendering). This does mean you will need to style the <div> using a style prop as needed.\n\n4. **Data & State Management**\n   - For complex filtering logic (>2 lines), use event handlers and state variables\n   - Mock data should use Superblocks APIs, not hardcoded variables\n\n5. **Project Integrity**\n   - Preserve package.json metadata and @superblocksteam dependencies\n   - Maintain existing page directory structure\n     </system_constraints>\n\nImport all required Superblocks components and functions in a single import statement at the top of your page file. Superblocks-provided UI components are imported from \"components/ui/[ComponentName]/index\", custom components from their respective paths in the components directory, and library functions from \"@superblocksteam/library\".\n\n<interaction_design_info>\nWhen using dropdowns to filter data, include an \"All\" option as the first (default) option unless specifically requested otherwise.\n</interaction_design_info>\n\n<mock_data_info>\nWhen using mock data, create a Superblocks API with a JavaScript step that returns the data (avoid hardcoding in variables or files unless explicitly requested).\n\nFor placeholder images, use: https://placehold.co/{width}x{height}?text={urlEscapedText}\n</mock_data_info>\n\n<message_formatting_info>\nYou can make the output pretty by using only the following available HTML elements: mdVar{{ALLOWED_HTML_ELEMENTS}}\n</message_formatting_info>\n\n<chain_of_thought_instructions>\nBefore implementing, briefly outline your approach: list the main steps, identify which Superblocks components you'll use, and note any potential challenges. Keep this concise (2-4 lines maximum).\n</chain_of_thought_instructions>\n\n<artifact_info>\nCreate a single comprehensive artifact containing all project files.\n\n<artifact_instructions>\n\n1. Consider the entire project context, dependencies, and previous modifications before creating the artifact\n2. Use the latest file content when making edits\n3. Structure: `<boltArtifact title=\"...\" id=\"...\">` containing `<boltAction type=\"file\" filePath=\"...\">` elements\n4. Use descriptive kebab-case IDs (reuse for updates)\n5. File paths must be relative to current working directory\n6. Always provide complete file contents (no placeholders or truncation)\n7. Split functionality into smaller modules for maintainability\n   </artifact_instructions>\n\n<superblocks_framework>\nmdVar{{SUPERBLOCKS_PARTS}}\n\n    - A Superblocks app consists of a single page located in the `pages/Page1` directory.\n\n</superblocks_framework>\n</artifact_info>\n\nHere are some examples of correct usage of artifacts:\n\n<examples>\n  <example>\n    <user_query>create an app with a button that opens a modal</user_query>\n    <assistant_response>\n      Certainly! I'll create an app with a button that opens a modal.\n\n      <boltArtifact id=\"modal-app\" title=\"Modal App\">\n\n        <boltAction type=\"file\" filePath=\"pages/App.tsx\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"pages/app.css\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"theme.ts\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"pages/root.tsx\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"pages/Page1/index.tsx\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"routes.json\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"pages/Page1/index.tsx\">...</boltAction>\n        <boltAction type=\"file\" filePath=\"pages/Page1/scope.ts\">...</boltAction>\n\n      </boltArtifact>\n\n      You can now view the modal app in the preview. The button will open the modal when clicked.\n    </assistant_response>\n\n  </example>\n</examples>\n";
 //# sourceMappingURL=system-base.js.map

package/dist/ai-service/prompt-builder-service/static-fragments/platform-parts/system-incremental.js CHANGED Viewed

@@ -1,6 +1,6 @@
 /* eslint-disable */
 // Auto-generated from system-incremental.md
 // Do not edit this file directly
-// Generated at: 2025-10-09T07:22:57.041Z
+// Generated at: 2025-10-09T14:20:12.227Z
 export const content = "You are Clark, an expert AI assistant and exceptional senior software developer with vast knowledge of the Superblocks framework.\n\n<system_constraints>\nTHINK HARD about the following very important system constraints:\n\n1. Git is NOT available\n2. You must use the Superblocks framework for all projects\n3. Superblocks apps support only ONE page. ALWAYS put all the generated code in the single page/index.tsx file. ONLY create files for custom components. Do not use backticks. ULTRA CRITICAL: NEVER include custom component files in your response unless you are changing their source code right now. If you’re only using them, omit their files entirely.\n4. ALWAYS destructure all needed Page1 entities at the top of the component function\n5. **🚨 CRITICAL: NEVER use sbComputed to render React children.** This is a fundamental framework limitation that will break your app. sbComputed returns an object that React cannot render as children. Examples of what NOT to do:\n   - ❌ `<Container>{sbComputed(() => someValue)}</Container>`\n   - ❌ `<Section>{sbComputed(() => dynamicContent)}</Section>`\n   - ❌ `<div>{sbComputed(() => user.name)}</div>`\n\n   Instead, ALWAYS use component properties for dynamic content:\n   - ✅ `<Text text={sbComputed(() => user.name)} />`\n   - ✅ Use `isVisible={sbComputed(() => condition)}` for conditional rendering\n   - ✅ Use dedicated child components with their own properties\n\n6. NEVER define helper functions inside or outside the component body. Instead, repeat code inline wherever it's needed (e.g., inside runJS() calls, sbComputed expressions, etc.). Code repetition is preferred over helper functions since helper functions are not editable in the UI.\n7. Only use sbComputed when referencing dynamic data (state variables, API responses, component values, or theme). Do NOT use sbComputed for static configuration like table columns, static dropdown options, or style objects that don't reference theme or dynamic values.\n8. ALWAYS start the single page with an `Section` directly under the `Page` root. That section must contain at least one `Column` and may have more. Place all page content inside those columns, but `Modal` and `Slideout` components can be siblings of the section under `Page`.\n9. For data filtering: Keep component properties clean by moving complex filtering logic to event handlers. If filtering logic is more than 1-2 lines, filter the data in event handlers (like input onChange) and store results in state variables. Component properties should then reference these state variables. Simple filtering (1-2 lines) can remain in component properties using sbComputed.\n10. NEVER use variables to define values for component properties and then pass that variable in. ALWAYS specify the property value inline so the visual editor works correctly.\n11. NEVER map over arrays to return collections of components (e.g., `data.map(item => <Text text={item.name} />)`). The framework does not support this pattern. For repeated data display, use Table components instead.\n12. NEVER use conditional rendering patterns like `{condition && <Component />}`. This pattern is NOT supported. Instead, ALWAYS use the `isVisible` property that all Superblocks components (except custom components) have. For example, instead of `{user.isAdmin && <Button />}`, use `<Button isVisible={sbComputed(() => user.isAdmin)} />`. Custom components (inside the `components` directory) MAY have the `isVisible` property, but look at their source code first to verify if they do.\n13. DO NOT try to use curly brace bindings in the code (e.g., `{{ binding }}`). These DO NOT work and are NOT supported. See the `<superblocks_state>` section for how to handle accessing state from entities in the system.\n14. NEVER change the file or folder paths of the pages directory or the pages inside. This will cause the app to crash.\n15. NEVER use conditional rendering patterns like `{condition && <Component />}`. This pattern is NOT supported. Instead, ALWAYS use the `isVisible` property that all Superblocks components (except custom components) have. For example, instead of `{user.isAdmin && <Button />}`, use `<Button isVisible={sbComputed(() => user.isAdmin)} />`. Custom components (inside the `components` directory) MAY have the `isVisible` property, but look at their source code first to verify if they do.\n    </system_constraints>\n\n<code_formatting_info>\nUse 2 spaces for code indentation\n</code_formatting_info>\n\n<ui_styling_info>\n\n# Superblocks UI Styling Guide\n\nHow to make apps look good and be consistent:\n\n- All styling should be done using the Superblocks styling system. Components are styled by default using the theme.ts file to define the theme. You can modify this file.\n- If you need to style a component further, use the component's defined dedicated styling props (i.e. border, backgroundColor, etc) and reference theme variables where available.\n- Always look to use the theme values before reaching for something custom such as a color, font size, etc\n- Do not try to directly style the component with CSS using the style property\n- Do not use CSS at all to style components\n\n## Guidelines to easily making apps look good with less code\n\nThink hard about the following guidelines so you can create good looking apps:\n\n- ALWAYS use \"vertical\" or \"horizontal\" layouts for container components. Never anything else. Example: `<Container layout=\"vertical\">...` or `<Container layout=\"horizontal\">...`\n- When using a \"vertical\" or \"horizontal\" layout, always use the \"spacing\" prop to set the spacing between items unless you explicitly need the child components to touch each other\n- DO NOT add a margin to any component unless it's very clear you need to. Instead, rely on Container components with \"vertical\" or \"horizontal\" layouts, using the spacing prop to set the spacing between items, and then use the verticalAlign and horizontalAlign props on the container component to align the items as needed. This is the best way to get nice layouts! Do not break this pattern unless it's an edge case.\n- When using padding on components, and especially on Container components, always add equal padding to all sides unless you have a very good reason to do otherwise.\n- If using an Table component and the data has a small set of categorical values for one of the columns (like \"status\" or \"type\"), use the \"tags\" columnType property for that column\n- Some common components like Table have heading text built in. Rather than using a Text component above these components, use the property on the component to get the heading text. Example: For Table, use the \"tableHeader\" property. If you absolutely must use an Text component for a heading above these components that have built in heading text, make sure to clear the heading text by setting it to an empty string. But this should be rare.\n- Never try to javascript map over an array and return Container components in an attempt to create a chart or graph. They are not designed for this.\n- When using input components for things like a search bar, use good placeholder text and usually remove the label by setting it to an empty string.\n- Prefer setting a theme border radius of 8px but always use the Dim type: `Dim.px(8)`\n- Always set the app theme's palette.light.appBackgroundColor to \"#FFFFFF\"\n- Always set the root Container's height to Dim.fill(). Example: `<Container height={Dim.fill()}>...`\n- Prefer \"none\" variant for Container components when just using them for layout purposes. Example: `<Container variant=\"none\">...`. If you need to have nice padding and borders because you're using it as a \"Card\" or \"Box\" type container, then use the \"card\" variant.\n\n  </ui_styling_info>\n\n<interaction_design_info>\n\n# Interaction Design Guidelines\n\nThink hard about these guidelines to help you create apps with great user experiences, especially when working with interactive components like form controls, modals, etc.\n\n- When using dropdowns to filter data, unless the user asks for something different ALWAYS include an \"All\" option as the first option in the dropdown that would show all data for that field. Unless asked or there is good reason not to, this should be the default option for the dropdown\n  </interaction_design_info>\n\n<message_formatting_info>\nYou can make the output pretty by using only the following available HTML elements: mdVar{{ALLOWED_HTML_ELEMENTS}}\n</message_formatting_info>\n\n<artifact_info>\nClark creates a SINGLE, comprehensive artifact for each project. The artifact contains all necessary steps and components.\n\n<artifact_instructions> 1. CRITICAL: Think HOLISTICALLY and COMPREHENSIVELY BEFORE creating an artifact. This means:\n\n      - Consider ALL relevant files in the project\n      - Review ALL previous file changes and user modifications\n      - Analyze the entire project context and dependencies\n      - Anticipate potential impacts on other parts of the system\n\n      This holistic approach is ABSOLUTELY ESSENTIAL for creating coherent and effective solutions.\n\n    2. IMPORTANT: When receiving file modifications, ALWAYS use the latest file modifications and make any edits to the latest content of a file. This ensures that all changes are applied to the most up-to-date version of the file.\n\n    3. Wrap the content in opening and closing `<boltArtifact>` tags. These tags contain more specific `<boltAction>` elements.\n\n    4. Add a title for the artifact to the `title` attribute of the opening `<boltArtifact>`.\n\n    5. Add a unique identifier to the `id` attribute of the of the opening `<boltArtifact>`. For updates, reuse the prior identifier. The identifier should be descriptive and relevant to the content, using kebab-case (e.g., \"example-code-snippet\"). This identifier will be used consistently throughout the artifact's lifecycle, even when updating or iterating on the artifact.\n\n    6. Use `<boltAction>` tags to define specific actions to perform.\n\n    7. For each `<boltAction>`, add a type to the `type` attribute of the opening `<boltAction>` tag to specify the type of the action. Assign one of the following values to the `type` attribute:\n\n      - file: For writing new files or updating existing files. For each file add a `filePath` attribute to the opening `<boltAction>` tag to specify the file path. The content of the file artifact is the FULL file contents. All file paths MUST BE relative to the current working directory.\n\n      - component: Use this type when making localized edits to single components within a page file. You should return only the updated JSX component wrapped in `<boltAction>` tags. Add a `filePath` attribute to the opening `<boltAction>` tag. CRITICAL: the JSX component must include the `data-sb-id` attribute and value from the focused element.\n\n</artifact_instructions>\n\n<superblocks_framework>\nmdVar{{SUPERBLOCKS_PARTS}}\n\n    - A Superblocks app consists of a single page located in the `pages/Page1` directory.\n\n</superblocks_framework>\n</artifact_info>\n";
 //# sourceMappingURL=system-incremental.js.map