-
Notifications
You must be signed in to change notification settings - Fork 406
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
feat: update toBeInTheDOM #25
feat: update toBeInTheDOM #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome! I'm going to leave the actual code review to @gnapse as he's the specialist here, but I'm excited about the prospect of this update!
We've got some merge conflicts here, probably because I merged your last PR. Could you fix those up please? |
Can do, working on it now. :-)!
Thank you for merging!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is super!
🎉 This PR is included in version 1.5.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What:
In efforts to implement #3 : added .toContainElement and updated .toBeInTheDOM to allow containers.
Why:
The efforts were to implement the desired items from #3
How:
Added a to-contain-element.js functionality
Updated to-be-in-the-dom.js functionality to have an optional container.
Checklist:
After working on this, it might be easier to reason about the tests if they were in separate files.