fix(services): exclude empty string fields in create and update operations

- Filter out object entries with empty string values before mutation calls
- Apply filtering for both dashboards and widgets services on create and update methods
- Ensure only meaningful data is sent to the backend avoiding empty strings
- Maintain type assertions for filtered objects to keep type safety

docs(migrations): add instructions for creating and applying custom SQL migrations

- Document how to create empty migrations with custom SQL using prisma migrate dev --create-only
- Provide examples of adding columns and indexes in custom migration files
- Explain how to apply pending migrations in development and production environments
- Detail steps to handle modified migrations before and after applying them
- Clarify migration application is a local developer responsibility, not automated on Vercel

feat(prisma): add unique partial indexes on Dashboard table with deletedAt filter

- Drop existing indexes if they exist before creating new ones
- Create unique indexes on userId and name, and on deviceId, excluding deleted entries
- Use conditional index creation to avoid conflicts or errors if indexes already exist

Author: EndyKaufman

README.md

@@ -115,6 +115,58 @@ The web application is deployed to Vercel, which is configured to automatically
 
 Database migrations are generated based on changes to the Prisma schema and applied from the local developer's computer. Migrations must be applied locally by the developer and are not automatically applied by Vercel during deployment.
 
+### Creating New Migrations with Custom SQL
+
+To create a new empty migration (without changing the Prisma schema):
+
+```bash
+cd web
+npx prisma migrate dev --name migration_name --create-only
+```
+
+This creates an empty migration file in the `web/prisma/migrations` directory that you can manually edit with custom SQL commands.
+
+Example of a custom migration file:
+```sql
+-- Add a new column to the User table
+ALTER TABLE "User" ADD COLUMN "lastLoginAt" TIMESTAMP(3);
+
+-- Create an index on the new column
+CREATE INDEX "User_lastLoginAt_idx" ON "User"("lastLoginAt");
+```
+
+### Applying Migrations
+
+To apply pending migrations to your development database:
+
+```bash
+cd web
+npx prisma migrate dev
+```
+
+For production environments, use:
+
+```bash
+cd web
+npx prisma migrate deploy
+```
+
+### Working with Modified Migrations
+
+If you've modified a migration but haven't committed it yet:
+
+1. **If you haven't applied the migration yet:**
+   - Simply edit the migration file as needed
+   - Run `npx prisma migrate dev` to apply your changes
+
+2. **If you've already applied the migration:**
+   - Reset your database: `npx prisma migrate reset`
+   - Edit the migration file as needed
+   - Apply the migration: `npx prisma migrate dev`
+
+3. **If you're working with a team and someone else has applied the original migration:**
+   - Create a new migration with your changes: `npx prisma migrate dev --name fix_previous_migration`
+   - This approach maintains consistency across team members
 ## Deploying to Vercel
 
 To deploy this project to Vercel:

web/README.md

@@ -97,8 +97,60 @@ Database migrations are generated based on changes to the Prisma schema and appl
 2. Run `./node_modules/.bin/prisma migrate dev` to generate and apply migrations locally
 3. Commit the generated migration files to version control
 
-Note: Migrations must be applied locally by the developer and are not automatically applied by Vercel during deployment.
+### Creating New Migrations with Custom SQL
+
+To create a new empty migration (without changing the Prisma schema):
+
+```bash
+npx prisma migrate dev --name add_new_feature --create-only
+```
+
+This creates an empty migration file in the `prisma/migrations` directory that you can manually edit with custom SQL commands.
+
+Example of a custom migration file (`prisma/migrations/20251208120000_add_new_feature/migration.sql`):
+```sql
+-- Add a new column to the User table
+ALTER TABLE "User" ADD COLUMN "lastLoginAt" TIMESTAMP(3);
 
+-- Create an index on the new column
+CREATE INDEX "User_lastLoginAt_idx" ON "User"("lastLoginAt");
+
+-- Add a default value for existing records
+UPDATE "User" SET "lastLoginAt" = NOW() WHERE "lastLoginAt" IS NULL;
+```
+
+### Applying Migrations
+
+To apply pending migrations to your development database:
+
+```bash
+npx prisma migrate dev
+```
+
+For production environments, use:
+
+```bash
+npx prisma migrate deploy
+```
+
+### Working with Modified Migrations
+
+If you've modified a migration but haven't committed it yet:
+
+1. **If you haven't applied the migration yet:**
+   - Simply edit the migration file as needed
+   - Run `npx prisma migrate dev` to apply your changes
+
+2. **If you've already applied the migration:**
+   - Reset your database: `npx prisma migrate reset`
+   - Edit the migration file as needed
+   - Apply the migration: `npx prisma migrate dev`
+
+3. **If you're working with a team and someone else has applied the original migration:**
+   - Create a new migration with your changes: `npx prisma migrate dev --name fix_previous_migration`
+   - This approach maintains consistency across team members
+
+Note: Migrations must be applied locally by the developer and are not automatically applied by Vercel during deployment.
 ## Prisma Setup
 
 This project uses Prisma as the ORM. After setting up your database:

web/prisma/migrations/20251208071504_update_uniq_indexes/migration.sql

@@ -0,0 +1,29 @@
+DO $$
+BEGIN
+    DROP INDEX IF EXISTS "UQ_DASHBOARD__USER_ID_NAME";
+EXCEPTION
+    WHEN undefined_object THEN
+        NULL;
+END
+$$;
+
+-- CreateIndex
+CREATE UNIQUE INDEX IF NOT EXISTS "UQ_DASHBOARD__USER_ID_NAME" ON "Dashboard"("userId", "name")
+WHERE
+    "deletedAt" IS NULL;
+
+--
+DO $$
+BEGIN
+    DROP INDEX IF EXISTS "UQ_DASHBOARD__DEVICE_ID";
+EXCEPTION
+    WHEN undefined_object THEN
+        NULL;
+END
+$$;
+
+-- CreateIndex
+CREATE UNIQUE INDEX IF NOT EXISTS "UQ_DASHBOARD__DEVICE_ID" ON "Dashboard"("deviceId")
+WHERE
+    "deletedAt" IS NULL;
+

web/src/app/services/dashboards.service.ts

@@ -52,15 +52,23 @@ export class DashboardsService {
   private trpc = injectTrpcClient();
 
   create(dashboard: CreateDashboardType) {
-    return this.trpc.dashboards.create.mutate(dashboard);
+    return this.trpc.dashboards.create.mutate(
+      Object.fromEntries(
+        Object.entries(dashboard).filter(([, value]) => value !== '')
+      ) as CreateDashboardType
+    );
   }
 
   read(id: string) {
     return this.trpc.dashboards.read.query({ id });
   }
 
   update(dashboard: UpdateDashboardType) {
-    return this.trpc.dashboards.update.mutate(dashboard);
+    return this.trpc.dashboards.update.mutate(
+      Object.fromEntries(
+        Object.entries(dashboard).filter(([, value]) => value !== '')
+      ) as UpdateDashboardType
+    );
   }
 
   delete(id: string) {

web/src/app/services/widgets.service.ts

@@ -14,15 +14,23 @@ export class WidgetsService {
   private trpc = injectTrpcPureClient();
 
   create(widget: CreateWidgetType) {
-    return this.trpc.widgets.create.mutate(widget);
+    return this.trpc.widgets.create.mutate(
+      Object.fromEntries(
+        Object.entries(widget).filter(([, value]) => value !== '')
+      ) as CreateWidgetType
+    );
   }
 
   read(id: string) {
     return this.trpc.widgets.read.query({ id });
   }
 
   update(widget: UpdateWidgetType) {
-    return this.trpc.widgets.update.mutate(widget);
+    return this.trpc.widgets.update.mutate(
+      Object.fromEntries(
+        Object.entries(widget).filter(([, value]) => value !== '')
+      ) as UpdateWidgetType
+    );
   }
 
   delete(id: string) {