-
Notifications
You must be signed in to change notification settings - Fork 46.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align React Native OSS/Test Feature Flags #28677
Conversation
export const enableDeferRootSchedulingToMicrotask = false; | ||
|
||
export const enableAsyncActions = true; | ||
|
||
export const alwaysThrottleRetries = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fwiw, i think if this is true and working we should keep it true to prevent any regressions that would sneak in before we can land the flag in the main fbsource bundle.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would feel better about that if I had confidence in the timeline with which we could enable this internally. However, I don't have that, and I would be worried about the possibility that tests are written against the current (non-final) behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In other words... testing something that we'll never ship (in its current state) is worse to me than testing something that is currently in production (even if it is something we want to move away from eventually).
Comparing: 23b32d3...e7db8ea Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show
|
I'm validating this internally with D55534399 before merging. |
## Summary Makes a few changes to align React Native feature flags for open source and internal test renderer configurations. * Enable `enableSchedulingProfiler` for profiling builds. * Align `ReactFeatureFlags.test-renderer.native.js` (with `ReactFeatureFlags.native-fb.js`). * Enable `enableUseMemoCacheHook`. * Enable `enableFizzExternalRuntime`. * Disable `alwaysThrottleRetries`. ## How did you test this change? Ran the following successfully: ``` $ yarn test $ yarn flow native $ yarn flow fabric ```
## Summary Makes a few changes to align React Native feature flags for open source and internal test renderer configurations. * Enable `enableSchedulingProfiler` for profiling builds. * Align `ReactFeatureFlags.test-renderer.native.js` (with `ReactFeatureFlags.native-fb.js`). * Enable `enableUseMemoCacheHook`. * Enable `enableFizzExternalRuntime`. * Disable `alwaysThrottleRetries`. ## How did you test this change? Ran the following successfully: ``` $ yarn test $ yarn flow native $ yarn flow fabric ``` DiffTrain build for commit 425f72b.
Summary
Makes a few changes to align React Native feature flags for open source and internal test renderer configurations.
enableSchedulingProfiler
for profiling builds.ReactFeatureFlags.test-renderer.native.js
(withReactFeatureFlags.native-fb.js
).enableUseMemoCacheHook
.enableFizzExternalRuntime
.alwaysThrottleRetries
.How did you test this change?
Ran the following successfully: