-
Notifications
You must be signed in to change notification settings - Fork 130
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
keepalive interval should run outside of Angular zone #113
Comments
I can issue a PR if needed. |
Do I understand correctly that no one can use protractor for testing his application once this package is used? Is there any workaround? |
There is actually. If you run |
Thanks!! It would be great if you made a pull request, then we can source that one directly. |
Will do in the nearest future. |
Submitted a pull request: #122 |
Fixes bug #113: Run keepalive setInterval outside NgZone
Whoops, this PR was merged and I think has been in the codebase for a while now. It's definitely in the 8.0.0 beta builds. |
…option ssr option instructs interrupt sources to ignore targets derived from global context such as window or document so they can be safely used in ssr/universal apps. Fixes #113
…option ssr option instructs interrupt sources to ignore targets derived from global context such as window or document so they can be safely used in ssr/universal apps. Fixes #113
I'm submitting a ... (check one with "x")
Current behavior
Keepalive interval is run inside Angular zone, which causes Testability to be unstable.
Expected behavior
Keepalive interval should not affect Testability state, i.e. run outside of Angular zone.
Minimal reproduction of the problem with instructions
keepalive.inteval(1000)
keepalive.start()
getAllAngularTestabilities()[0].isStable()
false
What is the motivation / use case for changing the behavior?
To let the e2e tests pass in applications that use keepalive.
Please tell us about your environment:
Windows 7, IntelliJ, npm, Angular dev server
2.0.0-beta.15 & 6.0.0-beta.3
5.2.11 & 6.1.2
all
all
node --version
=8.11.3
Suggested solution:
Keepalive interval function should be run outside of Angular zone, while onPing emission should run inside the Angular zone.
The text was updated successfully, but these errors were encountered: