-
Notifications
You must be signed in to change notification settings - Fork 148
screen.container undefined #156
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
Comments
Hi Pavel, thanks for opening this issue. Damn, we tried to fix something doesn’t even exist. I’ll take care of this one tomorrow morning. |
Reviewing the original issue, the problem seems to be that In that case then we should allow the render result to use the container, as there's no other way to access it. |
Yep, I just assumed container was available under Should be easy just to revert that fix. |
I will create a PR just reverting that one |
created! |
that makes sense 🤦♂️😅 Not sure if you should allow render to use container tho. https://kentcdodds.com/blog/common-mistakes-with-react-testing-library#using-container-to-query-for-elements |
@timdeschryver I think we need its own |
🎉 This issue has been resolved in version 3.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I agree @Belco90 , that's what I also meant to say |
caused by #150
screen
doesn't havecontainer
keyThe text was updated successfully, but these errors were encountered: