Skip to content

Conversation

@sophiebits
Copy link
Collaborator

I feel gross. Better ideas welcome.

@sophiebits
Copy link
Collaborator Author

(Non-additive test changes are just to improve test isolation.)

@sebmarkbage
Copy link
Collaborator

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.

@sebmarkbage
Copy link
Collaborator

(On top of the existing batchedUpdates and findDOMNode hacks)

@sophiebits
Copy link
Collaborator Author

We could probably have problems if we read the owner and call .getName() on it. Not sure what else.

Copy link
Collaborator

@sebmarkbage sebmarkbage left a 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.
@sophiebits
Copy link
Collaborator Author

Now that I fixed Flow it uses the ReactInstance type in the file so when we remove that we'll notice.

@sophiebits sophiebits merged commit 705c9bc into facebook:master Nov 30, 2016
tomocchino pushed a commit to zpao/react that referenced this pull request Dec 1, 2016
I feel gross. Better ideas welcome.
acusti pushed a commit to brandcast/react that referenced this pull request Mar 15, 2017
I feel gross. Better ideas welcome.
laurinenas pushed a commit to laurinenas/react that referenced this pull request May 28, 2018
I feel gross. Better ideas welcome.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants