[BUG] Locator.Filter has extra properties
See original GitHub issueI think we have a bug in the code generator. The LocatorFilterOptions has 3 properties: HasText
, HasTextString
and HasTextRegex
to represent hasText?: string | RegExp,
. I think we don’t need HasText
. And if this is expected it’s confusing for some users.
Issue Analytics
- State:
- Created 3 months ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Why am I getting an error "Object literal may only specify ...
1 Answer 1 ... As of TypeScript 1.6, properties in object literals that do not have a corresponding property in the type they're...
Read more >Locator | Playwright Java
Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page...
Read more >Active Directory user filter does not search nested groups
To get a recursive search, or to have AD check relations, extra properties need to be included to the filter. In this case,...
Read more >Qurey Media Service Assets Or Streaming Locators
Checking the documentation on Filtering, it looks like we limit the filtering of Streaming Locators to the following properties in v3 API. https ......
Read more >Playwright Filter Locator
The filter method narrows the existing locator according to its applied filter. You can use a text filter or locator filter, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi Dario!
This is actually expected and was introduced in https://github.com/microsoft/playwright-dotnet/pull/2387.
There is no difference, they are the same and there for connivence.