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(select): throwing additional errors if ngModel fails to initialize #5405

Merged
merged 1 commit into from Jul 9, 2017

Conversation

crisbeto
Copy link
Member

If the user has an md-select with an ngModel that doesn't have a name inside a form, the forms module will throw an error, however Material will also start throwing errors, which may cause confusion. These changes add a null check so our errors don't get mixed up with the forms error.

Fixes #5402.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 28, 2017
const fixture = TestBed.createComponent(InvalidSelectInForm);

// The first change detection run will throw the "ngModel is missing a name" error.
expect(() => fixture.detectChanges()).toThrow();
Copy link
Contributor

@kara kara Jun 29, 2017

Choose a reason for hiding this comment

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

Can you pass a regex to toThrowError to check which specific error is being thrown here?

expect(() => fixture.detectChanges()).toThrow();

// The secound run shouldn't throw selection-model related errors.
expect(() => fixture.detectChanges()).not.toThrow();
Copy link
Contributor

Choose a reason for hiding this comment

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

Typo: secound -> second

@kara kara assigned crisbeto and unassigned kara Jun 29, 2017
If the user has an `md-select` with an `ngModel` that doesn't have a name inside a form, the forms module will throw an error, however Material will also start throwing errors, which may cause confusion. These changes add a null check so our errors don't get mixed up with the forms error.

Fixes angular#5402.
Copy link
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

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

LGTM

@kara kara added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jun 29, 2017
@mmalerba mmalerba merged commit 372549c into angular:master Jul 9, 2017
@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
action: merge The PR is ready for merge by the caretaker 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.

md-select with ngModel requires name attribute (hasValue error)
4 participants