web/apps/dashboard/lib/trpc/routers/deploy/project/create.ts (1)

160-173: Guard the regional settings insert when regions is empty.

Drizzle ORM throws with 'values() must be called with at least one value' when .values([]) is passed. This code will fail project creation if the regions table is unseeded, since [prodEnvId, previewEnvId].flatMap(...) produces an empty array when regions is empty. Add a guard to avoid that failure mode.

Suggested minimal patch

         const regions = await tx.query.regions.findMany({ columns: { id: true } });
-        await tx.insert(schema.appRegionalSettings).values(
-          [prodEnvId, previewEnvId].flatMap((environmentId) =>
-            regions.map((r) => ({
-              workspaceId: ctx.workspace.id,
-              appId,
-              environmentId,
-              regionId: r.id,
-              replicas: 1,
-              createdAt: Date.now(),
-              updatedAt: Date.now(),
-            })),
-          ),
-        );
+        const regionalSettings = [prodEnvId, previewEnvId].flatMap((environmentId) =>
+          regions.map((r) => ({
+            workspaceId: ctx.workspace.id,
+            appId,
+            environmentId,
+            regionId: r.id,
+            replicas: 1,
+            createdAt: Date.now(),
+            updatedAt: Date.now(),
+          })),
+        );
+
+        if (regionalSettings.length > 0) {
+          await tx.insert(schema.appRegionalSettings).values(regionalSettings);
+        }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/apps/dashboard/lib/trpc/routers/deploy/project/create.ts` around lines
160 - 173, The insert into appRegionalSettings calls .values(...) with a
flattened array from regions and will throw if regions is empty; to fix, build
the payload array (e.g., map over regions for each of prodEnvId and
previewEnvId) and only call
tx.insert(schema.appRegionalSettings).values(payload) when payload.length > 0
(guarding against regions.length === 0), referencing the existing variables
regions, prodEnvId, previewEnvId, ctx.workspace.id and appId so no insert is
attempted with an empty array.

web/apps/dashboard/app/(app)/[workspaceSlug]/projects/[projectId]/components/glow-icon.tsx (1)

24-30: Minor: Redundant ternary branches.

The glowVisible logic has identical outcomes for glow === true in both transition branches ("animate-pulse opacity-20"). This could be simplified, but the current structure may be intentional for future differentiation.

♻️ Optional simplification

  const glowVisible = transition
-   ? glow
-     ? "animate-pulse opacity-20"
-     : "opacity-0 transition-opacity duration-300"
-   : glow
-     ? "animate-pulse opacity-20"
-     : "hidden";
+   ? glow
+     ? "animate-pulse opacity-20"
+     : "opacity-0 transition-opacity duration-300"
+   : glow
+     ? "animate-pulse opacity-20"
+     : "hidden";

If transition behavior should differ in the future, the current structure is fine. Otherwise:

- const glowVisible = transition
-   ? glow
-     ? "animate-pulse opacity-20"
-     : "opacity-0 transition-opacity duration-300"
-   : glow
-     ? "animate-pulse opacity-20"
-     : "hidden";
+ const glowVisible = glow
+   ? "animate-pulse opacity-20"
+   : transition
+     ? "opacity-0 transition-opacity duration-300"
+     : "hidden";

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@web/apps/dashboard/app/`(app)/[workspaceSlug]/projects/[projectId]/components/glow-icon.tsx
around lines 24 - 30, The conditional for glowVisible currently repeats the same
branch for glow === true; simplify by checking glow first: if glow is true
return "animate-pulse opacity-20", otherwise return transition ? "opacity-0
transition-opacity duration-300" : "hidden". Update the glowVisible assignment
(the variable named glowVisible that uses transition and glow) to use this
simplified logic so behavior is unchanged but redundant ternary branches are
removed.