-
Notifications
You must be signed in to change notification settings - Fork 50.2k
Updated docs examples/recommendations to use findDOMNode instead of getDOMNode #2802
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
|
Code change was already merged here: #2646 This new pull request is for the docs update. |
|
Maybe add it to the Top-Level API doc as well? |
|
Yea, let's add the toplevel doc. |
docs/docs/ref-03-component-specs.md
Outdated
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.
Let's kill this note completely.
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.
(ping)
|
Alright, lets address the notes and add this to the top level API docs, then we can merge this. |
324ccb4 to
61d2cf5
Compare
|
@zpao good to go? |
docs/docs/ref-01-top-level-api.md
Outdated
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 you just copy the text from here? http://facebook.github.io/react/docs/component-api.html#getdomnode
Maybe worth adding a note there too saying that React.findDOMNode is preferred.
036c843 to
d157895
Compare
d157895 to
030fc75
Compare
|
@spicyj better? |
|
@JSFB shipit |
Updated docs examples/recommendations to use findDOMNode instead of getDOMNode
Updated docs examples/recommendations to use findDOMNode instead of getDOMNode