-
Notifications
You must be signed in to change notification settings - Fork 47.5k
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
Revert #14756 changes to ReactFiberScheduler #14992
Conversation
This PR introduced some bugs in concurrent mode during internal testing. Until we figure out a proper solution, I'm going to try reverting it. Not totally certain this is sufficient to unbreak the bugs we found, but I'm using this branch to determine that.
@@ -172,19 +171,6 @@ export type Thenable = { | |||
then(resolve: () => mixed, reject?: () => mixed): mixed, | |||
}; | |||
|
|||
// Intentionally not named imports because Rollup would |
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.
Mind keeping these?
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.
They're not being used in this module anymore. Do you mean comment these lines out?
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'll comment them out so we don't forget next time we import Scheduler in this module
ReactDOM: size: -0.5%, gzip: 🔺+0.3% Details of bundled changes.Comparing: 59ef284...fbc9284 react-dom
react-art
react-native-renderer
react-test-renderer
react-reconciler
Generated by 🚫 dangerJS |
Ok after testing in a sandbox, I believe this fixes/unbreaks at least one of the bugs we found internally. |
With a note not to use named imports next time we import Scheduler in this module.
#14756 PR introduced some bugs in concurrent mode during internal testing. I believe it's specifically related to the changes to ReactFiberScheduler. Until we figure out a proper solution, I'm going to try reverting it.
Not totally certain this is sufficient to unbreak the bugs we found, but I'm using this branch to determine that.