@optimatech88/titomeet-shared-lib 1.0.33 → 1.0.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@optimatech88/titomeet-shared-lib",
-  "version": "1.0.33",
+  "version": "1.0.35",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "scripts": {

package/prisma/migrations/20250617111807_updated_notification_type/migration.sql

@@ -0,0 +1,13 @@
+-- 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 "NotificationType" ADD VALUE 'EVENT_VALIDATION';
+ALTER TYPE "NotificationType" ADD VALUE 'EVENT_REJECTION';
+ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT';
+ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT_APPROVAL';
+ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT_REJECTION';

package/prisma/migrations/20250716081532_added_newslettter/migration.sql

@@ -0,0 +1,13 @@
+-- CreateTable
+CREATE TABLE "Newsletter" (
+    "id" TEXT NOT NULL,
+    "email" TEXT NOT NULL,
+    "unsubscribedAt" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "Newsletter_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "Newsletter_email_key" ON "Newsletter"("email");

package/prisma/schema.prisma

@@ -301,6 +301,11 @@ enum NotificationType {
   NEW_MESSAGE
   EVENT_REMINDER
   EVENT_PARTICIPATION_CONFIRMATION
+  EVENT_VALIDATION
+  EVENT_REJECTION
+  EVENT_ASSIGNMENT
+  EVENT_ASSIGNMENT_APPROVAL
+  EVENT_ASSIGNMENT_REJECTION
 }
 
 enum ProviderStatus {
@@ -322,3 +327,13 @@ enum PaymentStatus {
   FAILED
   REFUNDED
 }
+
+
+model Newsletter {
+  id String @id @default(cuid())
+  email String @unique
+  unsubscribedAt DateTime?
+
+  createdAt DateTime @default(now())
+  updatedAt DateTime @updatedAt
+}