Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

chore(quitDriver): have quitDriver return a webdriver promise directly #3992

Merged
merged 1 commit into from
Jan 20, 2017

Conversation

sjelin
Copy link
Contributor

@sjelin sjelin commented Jan 20, 2017

Wrapping it in a q promise is blocking #3899

Closes #3902

Custom frameworks might not make this change but it'll be fine. It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.

Wrapping it in a `q` promise is blocking angular#3899

Closes angular#3902

Custom frameworks might not make this change but it'll be fine.  It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.
@juliemr
Copy link
Member

juliemr commented Jan 20, 2017

LGTM once Travis is happy.

@sjelin sjelin merged commit 132fb86 into angular:noCF Jan 20, 2017
sjelin added a commit that referenced this pull request Jan 23, 2017
#3992)

Wrapping it in a `q` promise is blocking #3899

Closes #3902

Custom frameworks might not make this change but it'll be fine.  It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.
sjelin added a commit that referenced this pull request Jan 26, 2017
#3992)

Wrapping it in a `q` promise is blocking #3899

Closes #3902

Custom frameworks might not make this change but it'll be fine.  It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.
sjelin added a commit to sjelin/protractor that referenced this pull request Jan 27, 2017
angular#3992)

Wrapping it in a `q` promise is blocking angular#3899

Closes angular#3902

Custom frameworks might not make this change but it'll be fine.  It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.
igniteram pushed a commit to igniteram/protractor that referenced this pull request Feb 21, 2017
angular#3992)

Wrapping it in a `q` promise is blocking angular#3899

Closes angular#3902

Custom frameworks might not make this change but it'll be fine.  It'll only be a
problem in edge cases and they probably weren't returning the right promise
before anyway.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants