-
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(radio): refactor tests and fix ngModel #443
Conversation
|
||
groupDebugElement = fixture.debugElement.query(By.directive(MdRadioGroup)); | ||
groupNativeElement = groupDebugElement.nativeElement; | ||
groupInstance = groupDebugElement.injector.get(MdRadioGroup); |
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.
Is this the same as groupDebugElement.componentInstance
?
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.
Nope; radio-group is a @Directive
rather than a @Component
, so it doesn't have a componentInstance
.
@robertmesserle addressed comments |
private _updateSelectedRadioFromValue(): void { | ||
// Update selected if different from current value. | ||
// If the value already matches the selected radio, no dothing. |
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.
Did you mean "do nothing"?
703129a
to
98c0ac2
Compare
* Initialize properties once content children are available. | ||
* This allows us to propagate relevant attributes to associated buttons. | ||
*/ | ||
ngAfterContentInit() { |
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.
Just curious, shouldn't this method be @internal
?
98c0ac2
to
63a9fd9
Compare
63a9fd9
to
672e205
Compare
Verbal lgtm from @robertmesserle |
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. |
R: @kara @robertmesserle
dirty
(vs.pristine
initially)touched
checked
directly on a radio button not updating the group'svalue
.change
event on initial setting of value at application load.@internal