This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
ElementFinder.prototype.then not returning a promise #1152
Labels
Comments
@hankduan we should probably wrap the returned function as an immediately-resolved promise. Can we do: ElementFinder.prototype.then = function(fn, errorFn) {
if (this.opt_actionResult_) {
return this.opt_actionResult_.then(fn, errorFn);
} else {
return webdriver.promise.fulfilled(fn(this)); // Change this line?
}
}; |
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Aug 4, 2014
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Aug 4, 2014
fixed in #1158 |
hankduan
added a commit
that referenced
this issue
Aug 5, 2014
committed with d15d35a |
Thanks for a very quick response |
bodyduardU
pushed a commit
to bodyduardU/protractor
that referenced
this issue
Dec 5, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would expect every .then call to return a promise.
Since the protractor test below passes, ElementFinder's then method clearly returns the return value of the succes function.
When reading the documentation: https://github.com/angular/protractor/blob/master/docs/api.md#elementfinderprototypethen
I get the impression that it should return a promise (or a then-able)
Maybe this is a design decision, if so I would like to know the reason.
On a side note: I am very happy with protractor and I enjoy seeing the progress it makes. Thanks
Protractor test on version 1.0.0
The text was updated successfully, but these errors were encountered: