Usage of exact option with *byRole queries #1192
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a note about using `exact` option with *byRole queries to enable fuzzy matching. Please see details of the issue here: testing-library/dom-testing-library#1157 Users may expect to use `exact: false` for substring matching whereas it doesn't affect the way of filtering out DOM nodes by accessible names.
✅ Deploy Preview for testing-library ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Co-authored-by: Tim Deschryver <[email protected]>
timdeschryver
approved these changes
Feb 3, 2023
|
@all-contributors please add @alleksei37 for docs |
|
I've put up a pull request to add @alleksei37! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a note about using
exactoption with *byRole queries to enable fuzzy matching. Please see details of the issue here:testing-library/dom-testing-library#1157
Users may expect to use
exact: falsefor substring matching whereas it doesn't affect the way of filtering out DOM nodes by accessible names.