[🐛 Bug]: element search commands like browser.$ and element.$ have incorrect types about webdriverio HOT 4 OPEN

I didn't get what exactly you mean, sorry. Do you mean that most of the time there's enough data in ChainablePromiseEvent?

WebdriverIO is able to resolve the chain of promises, so it only matters that you have 1 await at the beginning of the chain like await $('foo').$('bar').$('loo').click(). In this case the bar element is fetched once the foo query is resolved, then the loo element is fetched once the bar element is resolved and the actual click is done once loo is resolved. This has been battle tested and works pretty great even for arrays like await $('foo').$$('bar')[123].$('loo').click().

from webdriverio.

Thanks for raising the issue @shadowusr

It is worth to take a look at this again for v9 as it is quite confusing. The biggest drawback of the ChainablePromiseElement is that IDEs autocomplete element chains to things like await (await $('foo')).click(). The reason we have this separation is because we implement the ability to just do await $('foo').$('bar').click() later on and so properties of ChainablePromiseElement are all promises, e.g.

const elem = await $('foo')
console.log(elem.elementId) // returns a string
// while
const elem = $('foo')
console.log(elem.elementId) // returns a Promise<string>

Over time it turned out that it really doesn't matter to have WebdriverIO.Element properties resolved when accessing it. Therefor I suggest to make ChainablePromiseElement the new WebdriverIO.Element.

from webdriverio.

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!

from webdriverio.

Over time it turned out that it really doesn't matter to have WebdriverIO.Element properties resolved when accessing it.

I didn't get what exactly you mean, sorry. Do you mean that most of the time there's enough data in ChainablePromiseEvent?

I personally think being able to write $().$().click() is very convenient and hope this new solution won't lead to getting rid of it. Because that'd require changing a lot of tests code.

If it's possible to replace WebdriverIO.Element with ChainablePromiseElement while keeping this feature, and use this single type everywhere in commands, that'd be great for sure!

from webdriverio.