I'm submitting a ... (check one with "x")
Current behavior
Adding ngAfterViewChecked() { } (even if blank) to any Component causes infinite loop and server-render timesout.
Expected behavior
Let the zone stabilize and render the application.
Minimal reproduction of the problem with instructions
This branch here:
https://github.com/MarkPieszak/ng-universal-demo/tree/ngAfterViewChecked-bug
You can see the only addition was: https://github.com/MarkPieszak/ng-universal-demo/blob/ngAfterViewChecked-bug/src/app/app.component.ts#L24-L26
What is the motivation / use case for changing the behavior?
Lifecycle hooks fix.
Please tell us about your environment:
This happens in Node/express and also ASP.NET Core/Node
cc/ @alxhub @vikerman @gdi2290
I'm submitting a ... (check one with "x")
Current behavior
Adding
ngAfterViewChecked() { }(even if blank) to any Component causes infinite loop and server-render timesout.Expected behavior
Let the zone stabilize and render the application.
Minimal reproduction of the problem with instructions
This branch here:
https://github.com/MarkPieszak/ng-universal-demo/tree/ngAfterViewChecked-bug
You can see the only addition was: https://github.com/MarkPieszak/ng-universal-demo/blob/ngAfterViewChecked-bug/src/app/app.component.ts#L24-L26
What is the motivation / use case for changing the behavior?
Lifecycle hooks fix.
Please tell us about your environment:
This happens in Node/express and also ASP.NET Core/Node
Angular version: 4.x
Node (for AoT issues):
node --version= Any version (tested on 6.x, 7.x, 8.0)cc/ @alxhub @vikerman @gdi2290