wdi5 fluent async api vs wdio async api

[vobu]

Hi @vobu , the async api works quite well! 👍 One thing I found is, seems that a fluent "click" is not supported yet.

This one work:

const button = await myButton.getWebElement();
await myButton.click();

This one is not working:

await myButton.getWebElement().click();

Error:

Originally posted by @cwang1221 in #104 (reply in thread)

[vobu]

this is b/c you're working in wdio-native land here:
await myButton.getWebElement().click()

the equivalent with the wdi5 fluent async api would be:
await browser.asContro(buttonSelector).firePress()

[vobu]

@cwang1221
and i just got corrected on this by @Siolto: firePress() is considered no-good-practice, that's why we put in #138.
also, we'll make sure that await browser.asControl(selector).getWebElement().click() will work.

[github-actions]

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

[vobu]

we're still evaluating different ideas, the most recent being #179 - will come to a decision pretty soon.
what's always going to be possible is transitioning from wdi5-api to WedriverIO-api via .getWebElement()

[github-actions]

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

[vobu]

there's now 2 options:

1. use wdi5's getWebElement() to transition to the WebdriverIO api
2. use $() in the fluent async api for subsequent WebdriverIO api calls - e.g. await browser.asControl(iaSyncSelector).$().isDisplayed()