Skip to content

Usage of exact option with *byRole queries #1192

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 3, 2023
Merged

Usage of exact option with *byRole queries #1192

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7157512
Usage of exact option with *byRole queries
alleksei37 Dec 16, 2022
da0358b
Update docs/queries/about.mdx
alleksei37 Feb 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/queries/about.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,6 +295,8 @@ can contain options that affect the precision of string matching:
- `exact`: Defaults to `true`; matches full strings, case-sensitive. When false,
matches substrings and is not case-sensitive.
- `exact` has no effect on `regex` or `function` arguments.
- `exact` has no effect on accessible names specified with the `name` option of `*byRole`
queries. You can use a regex for fuzzy matching on accessible names.
- In most cases using a regex instead of a string gives you more control over
fuzzy matching and should be preferred over `{ exact: false }`.
- `normalizer`: An optional function which overrides normalization behavior. See
Expand Down