-
Notifications
You must be signed in to change notification settings - Fork 26.2k
Testability.whenStable does not work for chained http calls #20921
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
Labels
Milestone
Comments
alexeagle
pushed a commit
that referenced
this issue
Jan 17, 2018
#20924 was reverted. |
jbogarthyde
pushed a commit
to jbogarthyde/angular
that referenced
this issue
Feb 23, 2018
Fixes an issue where chained http calls would prematurely call testability whenStable callbacks after the first http call. Fixes angular#20921 PR Close angular#20924
leo6104
pushed a commit
to leo6104/angular
that referenced
this issue
Mar 25, 2018
Fixes an issue where chained http calls would prematurely call testability whenStable callbacks after the first http call. Fixes angular#20921 PR Close angular#20924
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
I'm submitting a...
Current behavior
When chaining http calls the testability.whenStable callback is run after the first http call is made
Expected behavior
The when stable callback should be run after the entire chain of http calls is completed
Minimal reproduction of the problem with instructions
I have produced a repository from a clean
ng new
where the e2e tests demonstrates this funcionality.https://github.com/lyml/chained-http
See also:
angular/protractor#4582
Where the problem is discussed in more detail.
What is the motivation / use case for changing the behavior?
Testabilitys whenStable is, as far as I can tell, only there to make test frameworks like protractor capable of determining when there are no more background tasks. This works properly for single http calls and chained setTimeout calls however for specifically http calls that trigger a new http call it incorrectly marks the testabity as stable.
Environment
The text was updated successfully, but these errors were encountered: