API key workaround

server/src/getTreatments.js

@@ -30,9 +30,14 @@ function validatePromptString({ filename, promptString }) {
   // Parse the prompt string into its sections
 
   // TODO: this replicates client-side code - is there a way to refactor that makes sense?
-  const sectionRegex = /---\n/g;
+
+  // Checking if promptString is empty
+  if (promptString.trim().length < 1) {
+    error("Prompt file string is empty");
+    throw new Error (`Prompt file string is empty. This could be because the returned file has no contents, or because the file fetch failed.`);
+  }
   const [, metaDataString, prompt, responseString] =
-    promptString.split(sectionRegex);
+    promptString.split(/^-{3,}$/gm);
   const metaData = loadYaml(metaDataString);
   const promptType = metaData?.type;
   const validPromptTypes = [

server/src/preFlight/preFlightChecks.js

@@ -1,10 +1,10 @@
 export function checkRequiredEnvironmentVariables() {
-  const requiredEnvVars = [
+
+  const requiredInProd = [
     "DAILY_APIKEY",
     "QUALTRICS_API_TOKEN",
     "QUALTRICS_DATACENTER",
     "DELIBERATION_MACHINE_USER_TOKEN",
-    "DATA_DIR",
     "GITHUB_PRIVATE_DATA_OWNER",
     "GITHUB_PRIVATE_DATA_REPO",
     "GITHUB_PRIVATE_DATA_BRANCH",
@@ -13,10 +13,23 @@ export function checkRequiredEnvironmentVariables() {
     "GITHUB_PUBLIC_DATA_BRANCH",
     "ETHERPAD_API_KEY",
     "ETHERPAD_BASE_URL",
-  ];
+  ]
+
+  // TEST_CONTROLS === "enabled" allows for dev
+  if (process.env.TEST_CONTROLS !== "enabled") {
+    for (const envVar of requiredInProd) {
+      if (!process.env[envVar] || process.env[envVar] === "none") {
+        throw new Error(`Missing required environment variable ${envVar}`);
+      }
+    }
+  }
+
+  const requiredInDevAndProd = [
+    "DATA_DIR",
+  ]
 
   // eslint-disable-next-line no-restricted-syntax
-  for (const envVar of requiredEnvVars) {
+  for (const envVar of requiredInDevAndProd) {
     if (!process.env[envVar]) {
       throw new Error(`Missing required environment variable ${envVar}`);
     }