Renamed outdated schedule/tracing referecnes (#14177)
Brian Vaughn committed
Nov 9, 2018 at 12:37 UTC
d5e1bf07d086e4fc1998653331adecddcd0f5274
2 files changed
+3
-3
packages/react-reconciler/src/ReactFiberScheduler.js
+2
-2
@@ -180,11 +180,11 @@ let warnAboutInvalidUpdates;
180
181
if (enableSchedulerTracing) {
182
// Provide explicit error message when production+profiling bundle of e.g. react-dom
183
- // is used with production (non-profiling) bundle of schedule/tracing
183
+ // is used with production (non-profiling) bundle of scheduler/tracing
184
invariant(
185
__interactionsRef != null && __interactionsRef.current != null,
186
'It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) ' +
187
- 'without also replacing the `schedule/tracing` module with `schedule/tracing-profiling`. ' +
187
+ 'without also replacing the `scheduler/tracing` module with `scheduler/tracing-profiling`. ' +
188
'Your bundler might have a setting for aliasing both modules. ' +
189
'Learn more at http://fb.me/react-profiling',
190
);
packages/react-reconciler/src/__tests__/ReactTracing-test.internal.js
+1
-1
@@ -11,7 +11,7 @@
11
'use strict';
12
13
describe('ReactTracing', () => {
14
- it('should error if profiling renderer and non-profiling schedule/tracing bundles are combined', () => {
14
+ it('should error if profiling renderer and non-profiling scheduler/tracing bundles are combined', () => {
15
jest.resetModules();
16
17
const ReactFeatureFlags = require('shared/ReactFeatureFlags');