-
Notifications
You must be signed in to change notification settings - Fork 50.1k
Refs between fiber and stack #8458
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
Conversation
|
(Non-additive test changes are just to improve test isolation.) |
|
So before we go down this line, do we have an idea of how many more of these issues we could face? Is it only going to be refs? What about warnings/hooks etc? If it's only refs then any hack seems isolated and fine but if it's going to be a few more maybe we need another approach. |
|
(On top of the existing batchedUpdates and findDOMNode hacks) |
|
We could probably have problems if we read the owner and call .getName() on it. Not sure what else. |
sebmarkbage
left a comment
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.
Can we mark these some how in a consistent way so that we know to revert them once stack is killed?
I feel gross. Better ideas welcome.
|
Now that I fixed Flow it uses the ReactInstance type in the file so when we remove that we'll notice. |
I feel gross. Better ideas welcome.
I feel gross. Better ideas welcome.
I feel gross. Better ideas welcome.
I feel gross. Better ideas welcome.