From 15c054a35e3148899823c0fb60fab5778daa951d Mon Sep 17 00:00:00 2001
From: William Grant <willmgrant@gmail.com>
Date: Mon, 3 Apr 2023 14:09:06 +0200
Subject: [PATCH] feat: added ability to reset the releaseFeature logic by
 updating the featureReleaseTimestamp

---
 ts/util/releaseFeature.ts | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/ts/util/releaseFeature.ts b/ts/util/releaseFeature.ts
index 1dac194a2..f7fbb5d8d 100644
--- a/ts/util/releaseFeature.ts
+++ b/ts/util/releaseFeature.ts
@@ -1,7 +1,8 @@
 import { Data } from '../data/data';
 
 // TODO update to agreed value between platforms
-const featureReleaseTimestamp = 1677488400; // unix 27/02/2023 09:00
+// const featureReleaseTimestamp = 1677488400000; // unix 27/02/2023 09:00
+const featureReleaseTimestamp = 1677661200000; // unix 01/03/2023 09:00
 let isFeatureReleased: boolean | undefined;
 
 /**
@@ -45,6 +46,15 @@ export async function checkIsFeatureReleased(featureName: string): Promise<boole
         });
       }
       return true;
+    } else {
+      // Reset featureReleased to false if we have already released a feature since we have updated the featureReleaseTimestamp to a later date.
+      // The alternative solution would be to do a db migration everytime we want to use this system.
+      if (featureAlreadyReleased) {
+        await Data.createOrUpdateItem({
+          id: 'featureReleased',
+          value: false,
+        });
+      }
     }
   }