Document use of redundant feature flag API call

github · Jan 6, 2022 · 9de1702 · 9de1702
1 parent efded22
commit 9de1702
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 1 deletion.
diff --git a/lib/analyze-action.js b/lib/analyze-action.js
diff --git a/lib/analyze-action.js.map b/lib/analyze-action.js.map
diff --git a/src/analyze-action.ts b/src/analyze-action.ts
@@ -111,6 +111,10 @@ async function run() {
       repositoryNwo,
       logger
     );
+    // We currently perform an API request in both the `init` and `analyze` Actions to determine
+    // what feature flags are enabled. At the time of writing, this redundant API call is acceptable
+    // to us, but if we wanted to avoid it, we could do so by serializing the feature flags as part
+    // of the config file.
     void featureFlags.preloadFeatureFlags();
 
     await runFinalize(outputDir, threads, memory, config, logger);