Skip to content
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.

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

Updated to use refs rather than findNode #486

Closed
wants to merge 1 commit into from

Conversation

thaggie
Copy link

@thaggie thaggie commented Apr 11, 2019

I have a situation where findNode was throwing an error because the node wasn't mounted yet.

@@ -357,6 +361,8 @@ class Transition extends React.Component {
delete childProps.onExiting
delete childProps.onExited

childProps.ref = this.setChildNode
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will override the ref that is attached to child.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And what about user component? Example

class Button extends React.Component {}

ref returned Symbol but not Element

@bensampaio
Copy link

@inomdzhon @eps1lon what's keeping this MR from being merged?

@inomdzhon
Copy link

@inomdzhon @eps1lon what's keeping this MR from being merged?

@bensampaio, this PR 559, no?

@silvenon silvenon closed this in #559 May 5, 2020
@jquense
Copy link
Collaborator

jquense commented May 5, 2020

🎉 This issue has been resolved in version 4.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants