Possible to use @connect functionality without wrapping it in a new component? #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Closed

thdxr opened this issue Jul 22, 2015 · 1 comment

thdxr commented Jul 22, 2015

This isn't a common use case but the connect decorator breaks the case when a parent component needs to call a child component's functions as documented here: https://facebook.github.io/react/tips/expose-component-functions.html

I agree it's better to handle these situations using flux or props but was curious to see whether or not this incompatibility can be avoided.

Contributor

gaearon commented Jul 31, 2015

We've decided to expose a way to access the instance (via a getUnderlyingRef() method). This will be in our API revamp from #16.

gaearon closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment