Bump react dep, move mockExecuteAction to avoid context warning #12
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
|
CLA is valid! |
koulmomo
added a commit
that referenced
this pull request
Mar 18, 2015
Bump react dep, move mockExecuteAction to avoid context warning
|
@ZeikJT I want to upgrade some more deps/devDeps before publishing a releasing |
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.
@koulmomo
Support React@0.13 or React@0.12
Had to update my test helper so that we wouldn't get erroneous warnings about context owner vs parent (stems from the fact that React calls
getChildContexttwice and looks for mismatches and since my function was nested it would create two different functions)