Booking status

package.json

@@ -1,6 +1,6 @@
 {
   "name": "nestjs-booking-system",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "license": "MIT",
   "author": "Michał Strumpf",
   "private": true,
@@ -78,9 +78,6 @@
     "typescript": "^5.9.2",
     "typescript-eslint": "^8.39.0"
   },
-  "prisma": {
-    "seed": "ts-node prisma/seed.ts"
-  },
   "jest": {
     "moduleFileExtensions": [
       "js",

prisma.config.ts

@@ -0,0 +1,7 @@
+import { defineConfig } from "prisma/config";
+
+export default defineConfig({
+  migrations: {
+    seed: `ts-node prisma/seed.ts`
+  }
+});

prisma/migrations/20250811112036_booking_status/migration.sql

@@ -0,0 +1,11 @@
+-- AlterEnum
+-- This migration adds more than one value to an enum.
+-- With PostgreSQL versions 11 and earlier, this is not possible
+-- in a single migration. This can be worked around by creating
+-- multiple migrations, each migration adding only one value to
+-- the enum.
+
+
+ALTER TYPE "public"."BookingStatus" ADD VALUE 'NO_SHOW';
+ALTER TYPE "public"."BookingStatus" ADD VALUE 'EXPIRED';
+ALTER TYPE "public"."BookingStatus" ADD VALUE 'COMPLETED';

prisma/schema.dbml

@@ -82,9 +82,12 @@ Enum UserRole {
 }
 
 Enum BookingStatus {
-  CONFIRMED
   PENDING
+  CONFIRMED
   CANCELLED
+  NO_SHOW
+  EXPIRED
+  COMPLETED
 }
 
 Enum ServiceStatus {

prisma/schema.prisma

@@ -88,9 +88,12 @@ enum UserRole {
 }
 
 enum BookingStatus {
-  CONFIRMED
   PENDING
+  CONFIRMED
   CANCELLED
+  NO_SHOW
+  EXPIRED
+  COMPLETED
 }
 
 enum ServiceStatus {