Add getNativeNode back, so we can get the native node when performing reorderings (instead of relyin#5784
Merged
jimfb merged 1 commit intofacebook:masterfrom Jan 5, 2016
Merged
Conversation
Contributor
Author
|
For @spicyj |
Collaborator
|
Oh, I did this already in #5782. Sorry for not coordinating. Removing the comment seems good though if you want to rebase. |
Contributor
|
@jimfb updated the pull request. |
…on is now different.
jimfb
added a commit
that referenced
this pull request
Jan 5, 2016
Add getNativeNode back, so we can get the native node when performing reorderings (instead of relyin
Contributor
|
@jimfb updated the pull request. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add getNativeNode back, so we can get the native node when performing reorderings (instead of relying on index).
This reverts commit 8eabf84.