From 0a2215cc0e3067087ff29644f4c50ee1fc69984b Mon Sep 17 00:00:00 2001
From: Andrew Clark <git@andrewclark.io>
Date: Wed, 11 Sep 2019 13:28:03 -0700
Subject: [PATCH] [Scheduler][www] Put profiling feature behind flag (#16757)

Our infra currently doesn't support loading a separate profiling
build of Scheduler. Until that's fixed, the recommendation is to load
a single build and gate the profiling feature behind a flag.

Alternative to #16659
---
 packages/scheduler/src/forks/SchedulerFeatureFlags.www.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/packages/scheduler/src/forks/SchedulerFeatureFlags.www.js b/packages/scheduler/src/forks/SchedulerFeatureFlags.www.js
index a1535868f1e6..e5d4cd05f8d7 100644
--- a/packages/scheduler/src/forks/SchedulerFeatureFlags.www.js
+++ b/packages/scheduler/src/forks/SchedulerFeatureFlags.www.js
@@ -9,7 +9,8 @@
 export const {
   enableIsInputPending,
   enableSchedulerDebugging,
+  enableProfiling: enableProfilingFeatureFlag,
 } = require('SchedulerFeatureFlags');
 
-export const enableProfiling = __PROFILE__;
+export const enableProfiling = __PROFILE__ && enableProfilingFeatureFlag;
 export const enableMessageLoopImplementation = true;