-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
fix(cdk/tree): react properly to expansion changes #29751
base: main
Are you sure you want to change the base?
fix(cdk/tree): react properly to expansion changes #29751
Conversation
c1115f6
to
433e357
Compare
} | ||
|
||
/** @docs-private */ | ||
@Directive({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is private, do we need a separate component for it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really sure of another way to hook into the onInit for the directive here, though I think ultimately removing mostRecentTreeNode
would solve this issue (e.g. doing data passing through injection)
1faed45
to
8b1d559
Compare
b138b69
to
cb4edf0
Compare
fixed the merge conflict |
Fixes #29669. This converts parts of the rendering pipeline to use signals which allows Angular to properly detect changes to the underlying data which may be caused by rendering new nodes. rxjs didn't handle this correctly as the data subscriptions were only set after the initial callback was run, causing partial updates.