using the updated way to get the dom node on react #19
Conversation
This file contains 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
Pomax
added a commit
that referenced
this pull request
Jul 22, 2015
using the updated way to get the dom node on react
|
thank you for the PR! |
|
This PR is a breaking change, unless React is defined globally, which cannot be assumed. Issue: #20 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The 'this.getDOMNode()' is deprecated and has been replaced with 'React.findDOMNode()'.
This point is also a impeditive to use it with the ES6 component that already don't has the getDOMNode.
I did a CodePen in onder to test it at least manually:
http://codepen.io/willgm/pen/oXPaov