Skip to content
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

Document deprecation of findDOMNode #1263

Merged
merged 1 commit into from
Oct 23, 2018
Merged

Document deprecation of findDOMNode #1263

merged 1 commit into from
Oct 23, 2018

Conversation

sebmarkbage
Copy link
Contributor

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.

@@ -50,6 +51,32 @@ Since object refs were largely added as a replacement for string refs, strict mo

[Learn more about the new `createRef` API here.](/docs/refs-and-the-dom.html)

### Warning about deprecated findDOMNode usage

React, used to support findDOMNode to search the tree for a DOM node given a class instance. Normally you don't need this because you can [attach a ref directly to a DOM node](/docs/refs-and-the-dom.html#creating-refs).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lose the first comma and backtick findDOMNode?

@reactjs-bot
Copy link

reactjs-bot commented Oct 16, 2018

Deploy preview for reactjs ready!

Built with commit 7bfb5e7

https://deploy-preview-1263--reactjs.netlify.com

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.
@gaearon gaearon merged commit b6b15d7 into reactjs:master Oct 23, 2018
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.

None yet

5 participants