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

Added alternative to findDOMNode #514

Closed

Conversation

AndrewMusgrave
Copy link

This approach provides an alternative to ReactDOM.findDOMNode for those who would like to enable React.StrictMode without console errors from react-transition-group.

@beefchimi
Copy link

@silvenon any chance this PR can get reviewed?

Copy link
Collaborator

@eps1lon eps1lon left a comment

Choose a reason for hiding this comment

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

How would I use this prop?


it('uses transitionNode when provided', () => {
const onEnterSpy = jest.fn();
const transitionNode = document.createElement('span');
Copy link
Collaborator

Choose a reason for hiding this comment

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

But that is not the element that is transitioning. It should be the child of Transition which is a div in this case.

Choose a reason for hiding this comment

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

should use ref

@JSteunou
Copy link

This is a good start to drop findDomNode without a massive breaking change like #559

Good transitional release before upgrading code base to the next major release

@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