-
Notifications
You must be signed in to change notification settings - Fork 470
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: Add extra error messages when screen
was passed instead of a DOM element
#949
feat: Add extra error messages when screen
was passed instead of a DOM element
#949
Conversation
- first step for fix issue: Output User Error instead of New Issue error for wrong node from user getWindowFromNode(node) addresses issue testing-library#911
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 84aaba9:
|
…ror for wrong node from user - by adding additional check and correct error-message according to edge use case from the issue testing-library#911
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: Tim Deschryver <28659384+timdeschryver@users.noreply.github.com>
Co-authored-by: Tim Deschryver <28659384+timdeschryver@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## main #949 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 26 26
Lines 962 966 +4
Branches 290 293 +3
=========================================
+ Hits 962 966 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
screen
was passed instead of a DOM element
@savcni01 Thanks! |
🎉 This PR is included in version 7.31.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Thank you! |
The PR is fix #911
When the user provides the wrong query (
screen
instead of a real query, we can output a clear, user-friendly error instead of general (and not relevant) - Create a new issue error.Checklist:
docs site