You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Change detection needs to fire a allViewChangesDone callback #3319
This would be similar to 'allChangesDone' but it will include any change detectors in the view tree.
It is needed for ViewQuery to fire its onChange callback guaranteeing it has all the directives that might have materialized in this CD turn. See failing test - rkirov@e543bab
onChange is called when after we dirty-check the bindings on injQ. onAllChangesDone is called after we dirty-check inj1 and inj2 (but before we dirty check inj3 and inj4).
We need a callback local to injQ to be called after we dirty-check all bindings in inj1, inj2 and the whole component view tree (inj3 and inj4).
The callback is still local to injQ, and not global.
Activity
mhevery commentedon Aug 20, 2015
I am confused, Are you suggesting that for
Queryto work it needs to wait for global CD to finish? That does not seem right. Can we chat about this?rkirov commentedon Aug 20, 2015
The name is unfortunate, I am not proposing anything global.
Imagine the following tree of injectors/nodes.
onChangeis called when after we dirty-check the bindings on injQ.onAllChangesDoneis called after we dirty-check inj1 and inj2 (but before we dirty check inj3 and inj4).We need a callback local to injQ to be called after we dirty-check all bindings in inj1, inj2 and the whole component view tree (inj3 and inj4).
The callback is still local to injQ, and not global.
mhevery commentedon Aug 21, 2015
I see, makes sense.
mhevery commentedon Aug 21, 2015
clearing assignee since no milestone.
rkirov commentedon Sep 4, 2015
fixed in 5ebeaf7
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.