-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(expectedConditions): update generic Function typings #5101
Conversation
9ea9bb4
to
63ca713
Compare
That worked! There was a bug in the test suite when setting the EC to a const. Since it is a global var it can be changed to a different instance. This is because the EC is tied to the browser, browsers are tied to the session. If you restart the browser or fork the browser, the const EC points to an old session. I am not sure how this passed in previous tests. We must have made a change recently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add changes tomorrow...
63ca713
to
0cf1d4c
Compare
Backed out Jasmine 3.3 changes for ExpectedConditions and other tsc errors. |
7530446
to
de72230
Compare
de72230
to
b2ceb36
Compare
b2ceb36
to
0aceb42
Compare
- Use `() => Promise<boolean>` over `Function` typings. - Fix an ExpectedConditions test where it was set to a const. - Fix a TypeScript typing interface issue with RunResults in taskRunner.
0aceb42
to
cee662a
Compare
() => Promise<boolean>
overFunction
typings.