[🐛 Bug]: Cannot command on elements coerced into an array: Malformed type for "elementId" parameter

[nextlevelbeard]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

latest

Node.js Version

20.11.1

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

Using the feature described in #8609 and implemented in #8736.

When coerceing elements into an element array and then mapping the elements to a command, it throws an error.

What is your expected behavior?

Feature #8609 should be working but appears to have regressed.

How to reproduce the bug.

// Should work, doesn't
const texts = await $$([
    $('.item'),
    $('button'),
    $('[data-value="hello"]')
]).map(e => e.getText())

// Workaround
const texts = await Promise.all([
    $('.item'),
    $('button'),
    $('[data-value="hello"]')
]).map(e => e.getText())

Relevant log output

Malformed type for "elementId" parameter of command getElementText
Expected: string
Actual: function

For more info see https://w3c.github.io/webdriver/#dfn-get-element-text

    at file:///Users/user/repos/repo/e2e/node_modules/webdriverio/build/commands/browser/waitUntil.js:43:15
    at async Browser.wrapCommandFn (file:///Users/user/repos/repo/e2e/node_modules/@wdio/utils/build/shim.js:90:29)
    at async Scenario.<anonymous> (file:///Users/user/repos/repo/e2e/steps/my.steps.ts:1:1)

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

[christian-bromann]

// Should work, doesn't

As per my comment the passed in elements can't be from type ChainablePromiseElement, so your example works if you do:

const texts = await $$([
    await $('.item'),
    await $('button'),
    await $('[data-value="hello"]')
]).map(e => e.getText())

I think it can be easily extended to support ChainablePromiseElement types as well. Contributions are welcome.

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!