Experimenting will exposing underlying component ref for access to component methods #1
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
… component. provide wrapper method to get underlying ref to provide access to unerlying refs methods
|
based on reduxjs#16 |
|
OK, I don't mind it. |
gnoff
added a commit
that referenced
this pull request
Jul 31, 2015
exposing underlying component ref for access to component methods via DecoratedComponent#getUnderlyingRef
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.
With the connect decorator the component you get back is a wrapper around the underlying component. If this underlying component has methods that are intended to be called by parents directly this gets int he way.
this PR is to expose the underlying ref via