Fix null node issue in ReactCSSTransitionGroup #6958
Merged
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
| this.classNameQueue.push(className); | ||
| this.nodeRef = nodeRef; |
There was a problem hiding this comment.
Is it ever possible that this is already set to a different node?
ghost
added
keyz
force-pushed
the
fix-css-transition-group
branch
from
414f38d
to
a899587
Compare
|
lgtm, thanks! |
|
@keyanzhang updated the pull request. |
zpao
pushed a commit
to zpao/react
that referenced
this pull request
Jun 8, 2016
(cherry picked from commit c9eb572)
zpao
pushed a commit
that referenced
this pull request
Jun 14, 2016
(cherry picked from commit c9eb572)
1 task
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.
Fixes #6619. Thanks for reviewing! CC @spicyj