Skip to content

Conversation

@dprevost-LMI
Copy link
Contributor

Fixes #1507.
Matchers toBeDisplayed and several others have TypeScript signatures that support an array element, even though they don't.

Comment on lines +24 to +25
- name: Run All Checks
run: npm run checks:all
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting on merge of #1991

return aliasFn.call(this, toExist, { verb: 'be', expectation: 'existing' }, el, options)
this.verb = 'be'
this.expectation = 'existing'
this.matcherName = 'toBeExisting'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed bad matcher name

const attr = await el.getAttribute(attribute)
if (typeof attr !== 'string') {
return { result: false, value: attr }
async function conditionAttributeValueMatchWithExpected(el: WebdriverIO.Element, attribute: string, expectedValue: string | RegExp | WdioAsymmetricMatcher<string>, options: ExpectWebdriverIO.StringOptions) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verify if Array<expectedValue: string | RegExp | WdioAsymmetricMatcher<string>> is need to allow to pass multiple different expected for the $$ support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

el?.isDisplayed is not a function

1 participant