Files
editor/packages/db
c476d30303 feat: enhance feedback form with image upload, user/project context, and scene graph (#113)
* feat: enhance feedback form with image upload, user/project context, and scene graph

- Add invisible drag-and-drop zone that reveals on hover+drag with dashed border overlay
- Multi-image upload (max 5, max 5MB each) to Supabase Storage feedback-images bucket
- Subtle attach button + thumbnail previews with remove on hover
- Auto-capture authenticated user email/name from Better Auth session
- Pass projectId from editor context
- Snapshot scene graph (nodes + rootNodeIds) on submit
- DB migration adds user_email, user_name, project_id, images (jsonb), scene_graph (jsonb) columns
- Storage bucket + RLS policies for public read / service role write

* refactor: use existing user_id FK instead of denormalized email/name columns

Removed user_email and user_name — the user_id already links to the users table.
Simpler schema, no data duplication.

* fix: guard against undefined in removeImage

* refactor: direct Supabase Storage upload via signed URLs

Bypass Vercel's 4.5MB serverless body-size limit by uploading images
directly from the client to Supabase Storage.

- New createImageUploadUrls server action generates signed upload URLs
- Client PUTs files directly to Supabase (no bytes through Vercel)
- submitFeedback now receives only image paths, not FormData with files
- No migration changes needed (existing RLS policies support signed URLs)

* fix: remove relative class that broke dialog centering

twMerge was replacing the Dialog's fixed positioning with relative,
pushing the dialog to the bottom of the viewport.

---------

Co-authored-by: Anton Pascal <anton-pascal@users.noreply.github.com>
2026-02-22 23:52:42 -05:00
..
2026-02-18 01:51:17 -05:00
2026-02-11 15:23:18 +09:00
2026-02-11 15:23:18 +09:00

@pascal-app/db

Database package for Pascal Editor with Supabase.

Setup

1. Install Dependencies

From the monorepo root:

bun install

This installs Supabase CLI as a dev dependency.

2. Start Supabase locally

From the monorepo root:

bun db:start

This will start a local Supabase instance with PostgreSQL, PostgREST, and Studio.

3. Check Supabase status

bun db:status

You'll see output like:

API URL: http://127.0.0.1:54321
DB URL: postgresql://postgres:postgres@127.0.0.1:54322/postgres
Studio URL: http://127.0.0.1:54323
Anon key: eyJh...
Service role key: eyJh...

4. Configure environment variables

Add these to apps/editor/.env.local:

# Supabase
NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NEXT_PUBLIC_SUPABASE_ANON_KEY=<your_anon_key>
SUPABASE_SERVICE_ROLE_KEY=<your_service_role_key>

# Better Auth
BETTER_AUTH_SECRET=<generate_with_openssl_rand_base64_32>
BETTER_AUTH_URL=http://localhost:3000

Generate a secret for BETTER_AUTH_SECRET:

openssl rand -base64 32

Migrations

Migrations are located in supabase/migrations/.

Apply migrations

bun db:reset  # Resets and applies all migrations

Create a new migration

cd packages/db
bunx supabase migration new <migration_name>

Database Schema

Auth Tables (Better Auth)

  • users - User accounts
  • sessions - Active sessions
  • accounts - OAuth provider accounts
  • verification_tokens - Magic link tokens

Application Tables

  • properties - User properties
  • properties_addresses - Property addresses with Google Maps data
  • properties_models - Scene graph models (versions)

Usage

Client-side (with RLS)

import { supabase } from '@pascal-app/db/client'

// RLS policies automatically filter by authenticated user
const { data } = await supabase.from('properties').select('*')

Server-side (service role)

import { supabaseAdmin } from '@pascal-app/db/server'

// Bypasses RLS - you must manually filter by user_id
const { data } = await supabaseAdmin
  .from('properties')
  .select('*')
  .eq('owner_id', userId)

Supabase Studio

Access the local Supabase Studio at: http://127.0.0.1:54323

Use this to:

  • Browse tables and data
  • Run SQL queries
  • View logs
  • Manage RLS policies