This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 230
Child queries for @deferred components are not properly reset when component is removed #1540
Comments
@leonsenft I am assuming this could be a known issue and fixed in 5.1/5.0.1, right? |
@leonsenft My guess is this is the same issue as #1539? |
Possibly, but IIRC I think we just don't generate the code to invalidate queries in this case. |
Oh but this example uses the correct template, unlike the issue #1539. |
Ah OK, good point. I'll take a look after #1539 in any case. |
I'm hoping this is just #1539, but I'll validate after. |
matanlurey
added a commit
to matanlurey/angular
that referenced
this issue
Aug 12, 2018
This does work after #1539, and I'm adding a test in matanlurey@b328544. |
matanlurey
added a commit
that referenced
this issue
Aug 13, 2018
Closes #1564 PiperOrigin-RevId: 208489962
matanlurey
added a commit
that referenced
this issue
Aug 13, 2018
Closes #1564 PiperOrigin-RevId: 208489962
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Consider the following example:
The
deferredChild
query is properly set with the deferred component when loaded; however, it's not reset to null when the enclosing structural directive removes the deferred component.The text was updated successfully, but these errors were encountered: