Better handling of the new phaseChangeNotifications field (defaults to true for all imports)

Author: jmgasper

migrator/prisma/schema.prisma

@@ -34,6 +34,7 @@ model Resource {
   memberId     String
   memberHandle String
   roleId       String
+  phaseChangeNotifications Boolean @default(true)
   createdAt    DateTime @default(now())
   createdBy    String
   updatedAt    DateTime? @updatedAt

migrator/src/migrators/migrateResource.js

@@ -51,9 +51,7 @@ async function migrateResource(filePath, startDate) {
       }
 
       const createdBy = data.createdBy || process.env.CREATED_BY;
-      const phaseChangeNotifications = Object.prototype.hasOwnProperty.call(data, 'phaseChangeNotifications')
-        ? data.phaseChangeNotifications
-        : null;
+      const phaseChangeNotifications = data.phaseChangeNotifications ?? true;
 
       await prisma.resource.upsert({
         where: { id: data.id },

migrator/src/migrators/migrateResourceBatch.js

@@ -46,9 +46,7 @@ async function migrateResource(filePath, startDate) {
     const results = await Promise.allSettled(
       batch.map(data => {
         const createdBy = data.createdBy || process.env.CREATED_BY;
-        const phaseChangeNotifications = Object.prototype.hasOwnProperty.call(data, 'phaseChangeNotifications')
-          ? data.phaseChangeNotifications
-          : null;
+        const phaseChangeNotifications = data.phaseChangeNotifications ?? true;
 
         return prisma.resource.upsert({
           where: { id: data.id },