Document deprecation of findDOMNode #1263
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gaearon
approved these changes
Oct 16, 2018
content/docs/strict-mode.md
Outdated
There was a problem hiding this comment.
Lose the first comma and backtick findDOMNode?
|
Deploy preview for reactjs ready! Built with commit 7bfb5e7 |
We might want to open an RFC for fragment refs which could solve the one remaining use case in a better way but at least let us get the deprecation in.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See facebook/react#13841
We might want to open an RFC for fragment refs which could solve the one remaining use case in a better way but at least let us get the deprecation in.