fix(Ref) Add a workaround for findDomNode to work with React 16.6.0 #3258
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.
This is a workaround for the following issue: #3255
React 16.6.0 throws an error if
findDOMNode
is called on an unmounted component which is the case inenzyme
'sshallow
component testing.Please consider this change as a temporary workaround until there's a better way to handle
findDOMNode
. React states that it's an antipattern to use it incomponentDidMount
.