-
Notifications
You must be signed in to change notification settings - Fork 467
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(waitForElementToBeRemoved): support passing an element directly #460
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 6fe2000:
|
Codecov Report
@@ Coverage Diff @@
## beta #460 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 412 419 +7
Branches 98 100 +2
=========================================
+ Hits 412 419 +7 Continue to review full report at Codecov.
|
Feel free to comment later if you have questions or feedback. We can address them before we publish beta. |
🎉 This PR is included in version 7.0.0-beta.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What: feat(waitForElementToBeRemoved): support passing an element directly
Why: Makes using this async utility simpler
How: Overload the argument for this so the callback can be a DOM node (or array of DOM nodes). In that case, we capture those and reassign the callback to a function that checks whether those are still contained in their original parent element
Checklist:
Really excited about this one.