@webstudio-is/postgrest 0.252.1

package/src/index.server.ts

@@ -0,0 +1,16 @@
+import type { Database } from "./__generated__/db-types";
+import { PostgrestClient } from "@supabase/postgrest-js";
+export type { Database } from "./__generated__/db-types";
+
+export type Client = PostgrestClient<Database>;
+
+export const createClient = (url: string, apiKey: string): Client => {
+  const client = new PostgrestClient<Database>(url, {
+    headers: {
+      apikey: apiKey,
+      Authorization: `Bearer ${apiKey}`,
+    },
+  });
+
+  return client;
+};

package/supabase/SQL-TESTS-AI.md

@@ -0,0 +1,161 @@
+# Sql Testing AI Helpers
+
+Extract schema
+
+```bash
+pnpx supabase db dump -s public --db-url postgresql://postgres:pass@localhost/webstudio > schema.sql
+```
+
+Promt Examples
+
+---
+
+Below is a partial dump of the SQL schema:
+
+```sql
+
+CREATE TABLE IF NOT EXISTS "public"."User" (
+    "id" "text" NOT NULL,
+    "createdAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "email" "text",
+    "image" "text",
+    "provider" "text",
+    "username" "text",
+    "teamId" "text"
+);
+
+
+CREATE TABLE IF NOT EXISTS "public"."Domain" (
+    "id" "text" NOT NULL,
+    "domain" "text" NOT NULL,
+    "createdAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "txtRecord" "text",
+    "status" "public"."DomainStatus" DEFAULT 'INITIALIZING'::"public"."DomainStatus" NOT NULL,
+    "error" "text",
+    "updatedAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS "public"."Build" (
+    "id" "text" NOT NULL,
+    "createdAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "pages" "text" NOT NULL,
+    "projectId" "text" NOT NULL,
+    "styleSources" "text" DEFAULT '[]'::"text" NOT NULL,
+    "styles" "text" DEFAULT '[]'::"text" NOT NULL,
+    "breakpoints" "text" DEFAULT '[]'::"text" NOT NULL,
+    "styleSourceSelections" "text" DEFAULT '[]'::"text" NOT NULL,
+    "props" "text" DEFAULT '[]'::"text" NOT NULL,
+    "instances" "text" DEFAULT '[]'::"text" NOT NULL,
+    "updatedAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "version" integer DEFAULT 0 NOT NULL,
+    "deployment" "text",
+    "publishStatus" "public"."PublishStatus" DEFAULT 'PENDING'::"public"."PublishStatus" NOT NULL,
+    "dataSources" "text" DEFAULT '[]'::"text" NOT NULL,
+    "lastTransactionId" "text",
+    "resources" "text" DEFAULT '[]'::"text" NOT NULL,
+    "marketplaceProduct" "text" DEFAULT '{}'::"text" NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS "public"."Project" (
+    "id" "text" NOT NULL,
+    "title" "text" NOT NULL,
+    "domain" "text" NOT NULL,
+    "userId" "text",
+    "isDeleted" boolean DEFAULT false NOT NULL,
+    "createdAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "previewImageAssetId" "text",
+    "marketplaceApprovalStatus" "public"."MarketplaceApprovalStatus" DEFAULT 'UNLISTED'::"public"."MarketplaceApprovalStatus" NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS "public"."ProjectDomain" (
+    "projectId" "text" NOT NULL,
+    "domainId" "text" NOT NULL,
+    "createdAt" timestamp(3) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
+    "txtRecord" "text" NOT NULL,
+    "cname" "text" NOT NULL
+);
+
+CREATE OR REPLACE FUNCTION "public"."latestBuildVirtual"("public"."Project") RETURNS SETOF "public"."latestBuildVirtual"
+    LANGUAGE "sql" STABLE ROWS 1
+    AS $_$ -- The function is expected to return 1 row
+
+
+SELECT
+    b.id AS "buildId",
+    b."projectId",
+    -- Use CASE to determine which domain to select based on conditions
+    CASE
+        WHEN (b.deployment::jsonb ->> 'projectDomain') = p.domain
+             OR (b.deployment::jsonb -> 'domains') @> to_jsonb(array[p.domain])
+        THEN p.domain
+        ELSE d.domain
+    END AS "domain",
+    b."createdAt",
+    b."publishStatus"
+FROM "Build" b
+JOIN "Project" p ON b."projectId" = p.id
+LEFT JOIN "ProjectDomain" pd ON pd."projectId" = p.id
+LEFT JOIN "Domain" d ON d.id = pd."domainId"
+WHERE b."projectId" = $1.id
+  AND b.deployment IS NOT NULL
+  -- 'destination' IS NULL for backward compatibility; 'destination' = 'saas' for non-static builds
+  AND ((b.deployment::jsonb ->> 'destination') IS NULL OR (b.deployment::jsonb ->> 'destination') = 'saas')
+  AND (
+      -- Check if 'projectDomain' matches p.domain
+      (b.deployment::jsonb ->> 'projectDomain') = p.domain
+      -- Check if 'domains' contains p.domain or d.domain
+      OR (b.deployment::jsonb -> 'domains') @> to_jsonb(array[p.domain])
+      OR (b.deployment::jsonb -> 'domains') @> to_jsonb(array[d.domain])
+  )
+ORDER BY b."createdAt" DESC
+LIMIT 1;
+
+$_$;
+
+```
+
+Create a pgTAP test for the function "public"."latestBuildVirtual" that takes "public"."Project" as an argument.
+
+---
+
+## Additional Instructions
+
+These instructions are sometimes necessary, while at other times they may not be required.
+
+All fields, such as `projectId`, already reference their corresponding table columns (e.g., `"Project"."id"`), but foreign key constraints are omitted.
+
+- **Data Integrity:** Do not create new tables for `"public"."Project"` or related entities. These tables already exist in the database. DO NOT TRUNCATE DROP or DELETE Existing tables.
+
+- **Data Accuracy:** When inserting new data, adhere strictly to the NULL constraints. Ensure all fields without default values are filled correctly in every `INSERT` statement.
+  you may omit fields with default values if they are not directly relevant to the tests, except for `"createdAt"` and `"updatedAt"` fields, which should always be specified with explicit timestamp values.
+
+- **Timestamp Fields:** For fields like `"createdAt"` and `"updatedAt"`, always use specific timestamp values rather than functions like `NOW()`.
+
+- **Naming Conventions:** Since field and function names use camelCase, always wrap them in double quotes (`""`) to ensure proper referencing.
+
+- **Test Coverage:** In addition to standard tests, cover additional cases to validate that the function returns the correct data in different scenarios:
+
+  1. When a project has changed its domain.
+  2. When builds with the new domain do not exist and when they do exist.
+  3. When the domain is either in `Build.deployment.projectDomain` or included in `Build.deployment.domains`.
+
+- **Function Calls:** Use precise casting for function calls, such as `(p.*)::Project`, to ensure accuracy in test execution.
+
+Ensure the tests comprehensively validate the function’s behavior in all specified cases.
+
+In addition to the specific test cases mentioned, any other test scenarios the model identifies would be highly appreciated.
+
+Examples of calling the function:
+
+```sql
+
+select "public"."latestBuildVirtual"((p.*)::"Project") from "public"."Project" p where p.id = '1';
+```
+
+---
+
+## PS
+
+Initially, it may produce non-working examples. However, it seems that a multi-step improvement process can enhance the results. By incorporating the additions mentioned above, you can achieve better final outcomes. While not perfect, it serves as a good starting point.
+
+Seems like the shorter the input the better the results. The models are seems to struggle with longer inputs.

package/supabase/tests/cleanup-builds.sql

@@ -0,0 +1,227 @@
+BEGIN;
+SET LOCAL search_path = pgtap, public;
+-- Initialize the testing environment without planning any specific number of tests
+-- We are using SELECT no_plan() because we don't specify the exact number of tests upfront.
+SELECT no_plan();
+
+-- =========================================
+-- Setup: Insert initial data for Users, Projects, Domains, ProjectDomains, and Builds
+-- =========================================
+
+-- Insert a user into the "User" table
+INSERT INTO "public"."User" ("id", "createdAt", "email", "username")
+VALUES
+  ('user1', '2023-01-01 00:00:00+00', 'user1@517cce32-9af3-example.com', 'user1');
+
+-- Insert projects associated with the user into the "Project" table
+INSERT INTO "public"."Project" ("id", "title", "domain", "userId", "isDeleted", "createdAt")
+VALUES
+  ('project1', 'Project One', '517cce32-9af3-project1-domain1', 'user1', false, '2023-01-01 00:00:00+00'),
+  ('project2', 'Project Two', '517cce32-9af3-project2-domain1', 'user1', false, '2023-01-01 00:00:00+00');
+
+-- Insert custom domains into the "Domain" table
+INSERT INTO "public"."Domain" ("id", "domain", "createdAt", "status", "updatedAt")
+VALUES
+  ('project-1-custom-domain-1', '517cce32-9af3-project-1-custom-domain-1.com', '2023-01-01 00:00:00+00', 'INITIALIZING', '2023-01-01 00:00:00+00'),
+  ('project-1-custom-domain-2', '517cce32-9af3-project-1-custom-domain-2.com', '2023-01-01 00:00:00+00', 'INITIALIZING', '2023-01-01 00:00:00+00'),
+  ('project-2-custom-domain-1', '517cce32-9af3-project-2-custom-domain-1.com', '2023-01-01 00:00:00+00', 'INITIALIZING', '2023-01-01 00:00:00+00'),
+  ('project-2-custom-domain-2', '517cce32-9af3-project-2-custom-domain-2.com', '2023-01-01 00:00:00+00', 'INITIALIZING', '2023-01-01 00:00:00+00');
+
+-- Establish relationships between projects and custom domains in the "ProjectDomain" table
+INSERT INTO "public"."ProjectDomain" ("projectId", "domainId", "createdAt", "txtRecord", "cname")
+VALUES
+  ('project1', 'project-1-custom-domain-1', '2023-01-01 00:00:00+00', 'txtRecord1', 'cname1'),
+  ('project1', 'project-1-custom-domain-2', '2023-01-01 00:00:00+00', 'txtRecord2', 'cname2'),
+  ('project2', 'project-2-custom-domain-1', '2023-01-01 00:00:00+00', 'p2-txtRecord1', 'cname1'),
+  ('project2', 'project-2-custom-domain-2', '2023-01-01 00:00:00+00', 'p2-txtRecord2', 'cname2');
+
+-- Insert initial builds into the "Build" table
+INSERT INTO "public"."Build" (
+    "id",
+    "createdAt",
+    "pages",
+    "projectId",
+    "deployment",
+    "updatedAt",
+    "publishStatus"
+)
+VALUES
+  -- Development Build for Project1
+  (
+    'build1-development',
+    '1990-01-01 00:00:00+00',
+    'home',
+    'project1',
+    NULL,
+    '1990-01-01 00:00:00+00',
+    'PENDING'
+  ),
+  -- Development Build for Project2
+  (
+    'project2-build1-development',
+    '1990-01-01 00:00:00+00',
+    'home',
+    'project2',
+    NULL,
+    '1990-01-01 00:00:00+00',
+    'PENDING'
+  ),
+  -- Custom Domain Build for Project2
+  (
+    'project2-build1-for-custom-domain-1',
+    '1990-01-02 00:00:00+00',
+    'home',
+    'project2',
+    '{"domains": ["517cce32-9af3-project-2-custom-domain-1.com"]}'::text,
+    '1990-01-02 00:00:00+00',
+    'PUBLISHED'
+  ),
+  -- Project Domain Build for Project2
+  (
+    'project2-build1-for-project-domain-1',
+    '1990-01-01 00:00:00+00',
+    'home',
+    'project2',
+    '{"domains": ["517cce32-9af3-project2-domain1"]}'::text,
+    '1990-01-01 00:00:00+00',
+    'PUBLISHED'
+  ),
+  -- Custom Domain Build for Project1
+  (
+    'build1-for-custom-domain-1',
+    '1990-01-02 00:00:00+00',
+    'home',
+    'project1',
+    '{"domains": ["517cce32-9af3-project-1-custom-domain-1.com"]}'::text,
+    '1990-01-02 00:00:00+00',
+    'PUBLISHED'
+  ),
+  -- Project Domain Build for Project1
+  (
+    'build1-for-project-domain-1',
+    '1990-01-01 00:00:00+00',
+    'home',
+    'project1',
+    '{"domains": ["517cce32-9af3-project1-domain1"]}'::text,
+    '1990-01-01 00:00:00+00',
+    'PUBLISHED'
+  );
+
+-- =========================================
+-- Test 1: Verify that initial cleanup does not clean any builds
+-- =========================================
+
+-- Run the database cleanup function for builds created in 1990
+SELECT database_cleanup('1990-01-01 00:00:00', '1990-12-31 23:59:59');
+
+-- Assert that no builds have been cleaned up initially
+SELECT is(
+  (SELECT count(*)::integer FROM "Build" WHERE "createdAt" BETWEEN '1990-01-01' AND '1990-12-31' AND "isCleaned" = TRUE),
+  0,
+  'Test 1: No builds should be cleaned up on initial cleanup'
+);
+
+-- =========================================
+-- Test 2: Insert a new project domain build and verify cleanup
+-- =========================================
+
+-- Insert a new build for the project domain
+INSERT INTO "public"."Build" (
+    "id",
+    "createdAt",
+    "pages",
+    "projectId",
+    "deployment",
+    "updatedAt",
+    "publishStatus"
+)
+VALUES
+  -- New Project Domain Build for Project1
+  (
+    'build2-for-project-domain-1',
+    '1990-01-02 00:00:00+00',  -- A later date than the previous build
+    'home',
+    'project1',
+    '{"domains": ["517cce32-9af3-project1-domain1"]}'::text,
+    '1990-01-02 00:00:00+00',
+    'PUBLISHED'
+  );
+
+-- Run the database cleanup function again
+SELECT database_cleanup('1990-01-01 00:00:00', '1990-12-31 23:59:59');
+
+-- Assert that one build has been cleaned (the previous project domain build)
+SELECT is(
+  (SELECT count(*)::integer FROM "Build" WHERE "createdAt" BETWEEN '1990-01-01' AND '1990-12-31' AND "isCleaned" = TRUE),
+  1,
+  'Test 2: Previous project domain build should be cleaned up after new build is published'
+);
+
+-- Assert that the specific build cleaned is 'build1-for-project-domain-1'
+SELECT is(
+  (SELECT id FROM "Build" WHERE "createdAt" BETWEEN '1990-01-01' AND '1990-12-31' AND "isCleaned" = TRUE),
+  'build1-for-project-domain-1',
+  'Test 2: Build "build1-for-project-domain-1" should be marked as cleaned'
+);
+
+-- =========================================
+-- Test 3: Insert a new custom domain build and verify cleanup
+-- =========================================
+
+-- Insert a new build for the custom domain
+INSERT INTO "public"."Build" (
+    "id",
+    "createdAt",
+    "pages",
+    "projectId",
+    "deployment",
+    "updatedAt",
+    "publishStatus"
+)
+VALUES
+  -- New Custom Domain Build for Project1
+  (
+    'build2-for-custom-domain-1',
+    '1990-01-03 00:00:00+00',  -- A later date than the previous build
+    'home',
+    'project1',
+    '{"domains": ["517cce32-9af3-project-1-custom-domain-1.com"]}'::text,
+    '1990-01-03 00:00:00+00',
+    'PUBLISHED'
+  );
+
+-- Run the database cleanup function again
+SELECT database_cleanup('1990-01-01 00:00:00', '1990-12-31 23:59:59');
+
+-- Assert that two builds have been cleaned (the previous project domain and custom domain builds)
+SELECT is(
+  (SELECT count(*)::integer FROM "Build" WHERE "createdAt" BETWEEN '1990-01-01' AND '1990-12-31' AND "isCleaned" = TRUE),
+  2,
+  'Test 3: Previous custom domain build should be cleaned up after new build is published'
+);
+
+-- Assert that the builds cleaned are 'build1-for-custom-domain-1' and 'build1-for-project-domain-1'
+SELECT results_eq(
+  $$
+      SELECT id FROM "Build" WHERE "createdAt" BETWEEN '1990-01-01' AND '1990-12-31' AND "isCleaned" = TRUE ORDER BY id
+  $$,
+  $$
+    SELECT * FROM (
+        VALUES
+            ('build1-for-custom-domain-1'),
+            ('build1-for-project-domain-1')
+    ) AS expected(id)
+    ORDER BY "id"
+  $$,
+  'Test 3: Builds "build1-for-custom-domain-1" and "build1-for-project-domain-1" should be marked as cleaned'
+);
+
+-- =========================================
+-- Finish the test
+-- =========================================
+
+-- Finish the test by calling the finish() function, which outputs the test summary
+SELECT finish();
+
+-- Rollback the transaction to ensure no changes are persisted in the database
+ROLLBACK;