-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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(expansion-panel): toggle not being updated when set programmatically #5650
fix(expansion-panel): toggle not being updated when set programmatically #5650
Conversation
abd3779
to
d58124c
Compare
panel.closed, | ||
filter.call(panel._inputChanges, changes => !!changes.hideToggle) | ||
) | ||
.subscribe(() => this._changeDetectorRef.markForCheck()); |
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.
Would it be possible to add a unit test for this case?
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 can give it a try, but I feel like the manual change detection might cause it not to fail as expected.
d58124c
to
9687d06
Compare
Added those unit tests as discussed @jelbourn. |
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.
LGTM
Fixes the toggle arrow not being flipped when the `expanded` is set programmatically, in addition to the `hideToggle` input not working either. This is a regression from angular#5549 and is a consequence of the fact that the panel header reaches into the panel to determine what to do with the arrow. Fixes angular#5623.
9687d06
to
d09d215
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes the toggle arrow not being flipped when the
expanded
is set programmatically, in addition to thehideToggle
input not working either. This is a regression from #5549 and is a consequence of the fact that the panel header reaches into the panel to determine what to do with the arrow.Fixes #5623.
Note: Similarly to #5631, if we want something more practical, we'll have to re-think where the input for these properties should go.