mirror of
https://github.com/zebrajr/react.git
synced 2025-12-07 12:20:38 +01:00
b928fc030a
* Move renderer `act` to work loop * Delete `flushSuspenseFallbacksInTests` This was meant to be a temporary hack to unblock the `act` work, but it quickly spread throughout our tests. What it's meant to do is force fallbacks to flush inside `act` even in Concurrent Mode. It does this by wrapping the `setTimeout` call in a check to see if it's in an `act` context. If so, it skips the delay and immediately commits the fallback. Really this is only meant for our internal React tests that need to incrementally render. Nobody outside our team (and Relay) needs to do that, yet. Even if/when we do support that, it may or may not be with the same `flushAndYield` pattern we use internally. However, even for our internal purposes, the behavior isn't right because a really common reason we flush work incrementally is to make assertions on the "suspended" state, before the fallback has committed. There's no way to do that from inside `act` with the behavior of this flag, because it causes the fallback to immediately commit. This has led us to *not* use `act` in a lot of our tests, or to write code that doesn't match what would actually happen in a real environment. What we really want is for the fallbacks to be flushed at the *end` of the `act` scope. Not within it. This only affects the noop and test renderer versions of `act`, which are implemented inside the reconciler. Whereas `ReactTestUtils.act` is implemented in "userspace" for backwards compatibility. This is fine because we didn't have any DOM Suspense tests that relied on this flag; they all use test renderer or noop. In the future, we'll probably want to move always use the reconciler implementation of `act`. It will not affect the prod bundle, because we currently only plan to support `act` in dev. Though we still haven't completely figured that out. However, regardless of whether we support a production `act` for users, we'll still need to write internal React tests in production mode. For that use case, we'll likely add our own internal version of `act` that assumes a mock Scheduler and might rely on hacks that don't 100% align up with the public one.
132 lines
5.1 KiB
JavaScript
132 lines
5.1 KiB
JavaScript
/**
|
|
* Copyright (c) Facebook, Inc. and its affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @flow strict
|
|
*/
|
|
|
|
// Filter certain DOM attributes (e.g. src, href) if their values are empty strings.
|
|
// This prevents e.g. <img src=""> from making an unnecessar HTTP request for certain browsers.
|
|
export const enableFilterEmptyStringAttributesDOM = false;
|
|
|
|
// Helps identify side effects in render-phase lifecycle hooks and setState
|
|
// reducers by double invoking them in Strict Mode.
|
|
export const debugRenderPhaseSideEffectsForStrictMode = __DEV__;
|
|
|
|
// To preserve the "Pause on caught exceptions" behavior of the debugger, we
|
|
// replay the begin phase of a failed component inside invokeGuardedCallback.
|
|
export const replayFailedUnitOfWorkWithInvokeGuardedCallback = __DEV__;
|
|
|
|
// Warn about deprecated, async-unsafe lifecycles; relates to RFC #6:
|
|
export const warnAboutDeprecatedLifecycles = true;
|
|
|
|
// Gather advanced timing metrics for Profiler subtrees.
|
|
export const enableProfilerTimer = __PROFILE__;
|
|
|
|
// Record durations for commit and passive effects phases.
|
|
export const enableProfilerCommitHooks = false;
|
|
|
|
// Trace which interactions trigger each commit.
|
|
export const enableSchedulerTracing = __PROFILE__;
|
|
|
|
// SSR experiments
|
|
export const enableSuspenseServerRenderer = __EXPERIMENTAL__;
|
|
export const enableSelectiveHydration = __EXPERIMENTAL__;
|
|
|
|
// Flight experiments
|
|
export const enableBlocksAPI = __EXPERIMENTAL__;
|
|
|
|
// Only used in www builds.
|
|
export const enableSchedulerDebugging = false;
|
|
|
|
// Disable javascript: URL strings in href for XSS protection.
|
|
export const disableJavaScriptURLs = false;
|
|
|
|
// Experimental React Flare event system and event components support.
|
|
export const enableDeprecatedFlareAPI = false;
|
|
|
|
// Experimental Host Component support.
|
|
export const enableFundamentalAPI = false;
|
|
|
|
// Experimental Scope support.
|
|
export const enableScopeAPI = false;
|
|
|
|
// Experimental useEvent support.
|
|
export const enableUseEventAPI = false;
|
|
|
|
// New API for JSX transforms to target - https://github.com/reactjs/rfcs/pull/107
|
|
|
|
// We will enforce mocking scheduler with scheduler/unstable_mock at some point. (v17?)
|
|
// Till then, we warn about the missing mock, but still fallback to a legacy mode compatible version
|
|
export const warnAboutUnmockedScheduler = false;
|
|
|
|
// Add a callback property to suspense to notify which promises are currently
|
|
// in the update queue. This allows reporting and tracing of what is causing
|
|
// the user to see a loading state.
|
|
// Also allows hydration callbacks to fire when a dehydrated boundary gets
|
|
// hydrated or deleted.
|
|
export const enableSuspenseCallback = false;
|
|
|
|
// Part of the simplification of React.createElement so we can eventually move
|
|
// from React.createElement to React.jsx
|
|
// https://github.com/reactjs/rfcs/blob/createlement-rfc/text/0000-create-element-changes.md
|
|
export const warnAboutDefaultPropsOnFunctionComponents = false;
|
|
|
|
export const disableSchedulerTimeoutBasedOnReactExpirationTime = false;
|
|
|
|
export const enableTrustedTypesIntegration = false;
|
|
|
|
// Controls sequence of passive effect destroy and create functions.
|
|
// If this flag is off, destroy and create functions may be interleaved.
|
|
// When the flag is on, all destroy functions will be run (for all fibers)
|
|
// before any create functions are run, similar to how layout effects work.
|
|
// This flag provides a killswitch if that proves to break existing code somehow.
|
|
export const runAllPassiveEffectDestroysBeforeCreates = false;
|
|
|
|
// Controls behavior of deferred effect destroy functions during unmount.
|
|
// Previously these functions were run during commit (along with layout effects).
|
|
// Ideally we should delay these until after commit for performance reasons.
|
|
// This flag provides a killswitch if that proves to break existing code somehow.
|
|
//
|
|
// WARNING This flag only has an affect if used with runAllPassiveEffectDestroysBeforeCreates.
|
|
export const deferPassiveEffectCleanupDuringUnmount = false;
|
|
|
|
// Enables a warning when trying to spread a 'key' to an element;
|
|
// a deprecated pattern we want to get rid of in the future
|
|
export const warnAboutSpreadingKeyToJSX = false;
|
|
|
|
export const enableComponentStackLocations = __EXPERIMENTAL__;
|
|
|
|
// Internal-only attempt to debug a React Native issue. See D20130868.
|
|
export const throwEarlyForMysteriousError = false;
|
|
|
|
export const enableNewReconciler = false;
|
|
|
|
// --------------------------
|
|
// Future APIs to be deprecated
|
|
// --------------------------
|
|
|
|
// Prevent the value and checked attributes from syncing
|
|
// with their related DOM properties
|
|
export const disableInputAttributeSyncing = false;
|
|
|
|
export const warnAboutStringRefs = false;
|
|
|
|
export const disableLegacyContext = false;
|
|
|
|
// Disables children for <textarea> elements
|
|
export const disableTextareaChildren = false;
|
|
|
|
export const disableModulePatternComponents = false;
|
|
|
|
// We should remove this flag once the above flag becomes enabled
|
|
export const warnUnstableRenderSubtreeIntoContainer = false;
|
|
|
|
// Modern event system where events get registered at roots
|
|
export const enableModernEventSystem = false;
|
|
|
|
// Support legacy Primer support on internal FB www
|
|
export const enableLegacyFBSupport = false;
|