Replaced ReacDOM.findDOMNode by using ref #57
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
|
Thanks for merging @cheton! Regards! |
|
Published v1.5.0. Thank you! |
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.
I opened this PR because I found myself with an issue when working with React & React DOM versions 16.2.0.
The error message was
Uncaught Sortable:
elmust be HTMLElement, and not [object null]and I fixed it by replacing the use of ReacDOM.findDOMNode with a ref attribute associated to the wrapping component rendered which seems to be the more appropriate way to reference an underlying DOM element with newer React versions (https://reactjs.org/docs/react-dom.html#finddomnode)