Skip to content
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/403/radio without name #478

Merged
merged 2 commits into from
May 25, 2016
Merged

Fix/403/radio without name #478

merged 2 commits into from
May 25, 2016

Conversation

robertmesserle
Copy link
Contributor

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 19, 2016
private _name: string = `md-radio-group-${_uniqueIdCounter++}`;

/** @internal */
nameEmitter: EventEmitter<string> = new EventEmitter<string>();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of this, could each radio pull the group's name in its own ngOnInit, and then the group can update them all whenever its name changes (in the setter)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That could work - that was kind of what I was suggesting when we spoke earlier when I wasn't sure if I liked the approach I took here.

Using *ngFor to iterate over options was causing the error "Expression has changed after it was checked. Previous value: undefined."

closes #403
@robertmesserle
Copy link
Contributor Author

@jelbourn Comments addressed

@jelbourn
Copy link
Member

LGTM

@jelbourn jelbourn merged commit d83f062 into angular:master May 25, 2016
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants