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

docs(input): remove extra parens and fix nits #6614

Merged
merged 1 commit into from
Aug 24, 2017

Conversation

willshowell
Copy link
Contributor

No description provided.

@willshowell willshowell requested a review from mmalerba as a code owner August 23, 2017 19:55
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 23, 2017
@@ -14,7 +14,7 @@ elements inside `md-form-field` as well. This includes Angular directives such a

The only limitations are that the `type` attribute can only be one of the values supported by
`mdInput` and the native element cannot specify a `placeholder` attribute if the `md-form-field`
also contains a `md-placeholder` element.
also contains an `md-placeholder` element.
Copy link
Contributor

Choose a reason for hiding this comment

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

a was correct, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Arguably haha. I'm basing it on the pronunciation of "md" sounding like "em dee". See APA blog referencing the subject.

@@ -129,18 +129,18 @@ the error messages.
function myErrorStateMatcher(control: FormControl, form: FormGroupDirective | NgForm): boolean {
// Error when invalid control is dirty, touched, or submitted
const isSubmitted = form && form.submitted;
return !!(control.invalid && (control.dirty || control.touched || isSubmitted)));
return !!(control.invalid && (control.dirty || control.touched || isSubmitted));
Copy link
Contributor

Choose a reason for hiding this comment

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

The coercion here seems to be unnecessary since all fields are boolean.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah it is unnecessary, but it's based on the default errorStateMatcher which originates from #3560 (comment).

Happy to change it if coercion is unnecessary, but it does add a little type safety. A little more discussion in #6585

Copy link
Member

Choose a reason for hiding this comment

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

It has an effect because isSubmitted is potentially undefined (if form is undefined)

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -129,18 +129,18 @@ the error messages.
function myErrorStateMatcher(control: FormControl, form: FormGroupDirective | NgForm): boolean {
// Error when invalid control is dirty, touched, or submitted
const isSubmitted = form && form.submitted;
return !!(control.invalid && (control.dirty || control.touched || isSubmitted)));
return !!(control.invalid && (control.dirty || control.touched || isSubmitted));
Copy link
Member

Choose a reason for hiding this comment

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

It has an effect because isSubmitted is potentially undefined (if form is undefined)

@jelbourn jelbourn added docs This issue is related to documentation pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 23, 2017
@kara kara merged commit f104101 into angular:master Aug 24, 2017
@willshowell willshowell deleted the patch-3 branch August 24, 2017 17:15
@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 docs This issue is related to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants