Protractor to v7 Typescript conversion #20
Unanswered
berdal84
asked this question in
Migration Issue
Replies: 2 comments 3 replies
-
For my last point, I just saw the alias is not the problem. Translation is manual I assume. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Good idea, added as requirement for #11
Yeah, so rather than let the compiler fail, have it add a throw exception. This way it makes it easier to test for sure. Mind creating an issue for it?
Let's create an issue for it to add TypeScript types where ever possible.
So currently the mod translates: const EC = protractor.ExpectedConditions; into const EC = require('wdio-wait-for') which is our drop in replacement. Are you saying you import it this way: import { EC } from 'protractor' ? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I just tried the last version (0.9.0) and I have some comments/suggestions to make.
--tsx
) since source extension is alwaysts
?browser.actions()
(incompatible with wdio API), I suggest to comment those lines and maybe add a// TODO: convert to wdio
(with the documentation link) and/or to add a `throw new Error('Convert the following commented lines to wdio.'); to avoid to miss it.ElementFinder
=>Promise<WebdriverIO.Element>
)browser.waitUntil(EC.presenceOf(toolBtn))
Do you plan to handle this later ?Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions