validation errors in md-autocomplete

[javierpavon2000]

I want to configure a md-autocomplete input as required and show a message if not filled, but it's not working

<md-autocomplete name="autocompleteName" ...      >
</md-autocomplete>
<div ng-messages="form.autompleteName.$error">
     <div ng-message="required">This is required!</div>
</div>

if I inspect the formController object for the form, there isn't any object for autocompleteName

any hint? any help?
I just want to validate the md-autocomplete following as the same way of the inputs, is it possible?

[hitigon]

made my own autocomplete component, which links ng-messages into it

[javierpavon2000]

Just, I can do it too, but I would prefer to follow the "standard" way like the others inputs

[hitigon]

@javierpavon2000 I prefer that too, but the md-autocomplete is inconsistent with md-input, that's I really don't like.

[bfelda]

@hitigon Agreed on it's inconsistency with md-input. Seems like it is currently designed to resemble a md-select instead of a md-input. It looks really odd with other md-input elements around it.

[robertmesserle]

@hitigon @javierpavon2000 @bfelda I just added a styling option for use in standard forms: f487248

I will be adding validation support as well.

[robertmesserle]

A demo of the new styles can be seen here: https://material.angularjs.org/#/demo/material.components.autocomplete

[hitigon]

@robertmesserle awesome job!

[robertmesserle]

Proposed syntax for ng-messages:

<md-autocomplete md-search-text="searchText" required>
  <md-item-template>...</md-item-template>
  <div ng-messages="searchText.$error">
    <div ng-message="required">This field is required</div>
  </div>
</md-autocomplete>

[111crb111]

Please, can you make some example with validations ? And what is md-item-template ?

[datak1d]

+1 for md-autocomplete validation example with md-item-template

[gpopovic]

+1 with validation example

[lillylykho]

+1

[bfelda]

@robertmesserle This looks great! Thanks for implementing it.

[gpopovic]

@bfelda this is going to be solved in 0.9.0?

[robertmesserle]

@gpopovic This is not going to be in 0.9.0, but I submitted a Pull Request for this feature: #2664

[bopm]

👍

[fabiusss]

+1

[pencilcheck]

At master, still no validation for md-autocomplete. The example doesn't work.

[MetalHexx]

Opened a new issue for this bug since it still appears to be broken: #3401

[caok2709]

Yes that's it. It's not working for md-autocomplete validation:

[caok2709]

Even if you said it's required.... $error will always be empty.

[SergeyBukhman]

There's a bug with the documentation and example. Instead of 'md-input-name' the documentation says 'name' and the example says 'input-name'.

[MetalHexx]

@SergeyBukhman - to be clear, "name", "md-input-name", and "input-name" all do not work.

[Luxiyalu]

md-input-name works as of 0.10.0. Documentation for it is seriously misleading.

[MetalHexx]

Md-input-name does not work for me. Anyone have a plunk or codepen showing it working?

[deckikwok]

+1. not working on 0.10.0.

[MetalHexx]

He's resolving it off issue #3401

[danieladz]

md-input-name="autocompleteInputName" worked for me, you should attach the error to the input inside de md-autocomplete.
now my problem is that the field is shown in red from the start, because is not $pristine u_u

[evoker]

This doesn't seem to be working in RC5 for 0.10.1

[chrisguerrero]

+1

md-input-name and required don't work for me either with 0.10.0

My temporary solution was to add a hidden input with the same model as md-selected-item

[alo]

+1

[jibiabraham]

@MetalHexx md-input-name is the right attribute to use.
Additionally, for usage along with ng-messages (when ng-messages are added within the autocomplete), you need to use floating labels via md-floating-label

[getuliojr]

I haven´t got this to work and the one that is present in the DEMO page is also not working for the required field. I appreciate if anyone has an idea about it.

[GustavSt]

Indeed, When seemingly doing everything right, the error message is shown from start, like @danieladz stated

[GustavSt]

I realized I get more weird behavior when trying to have validations when the md-autocomplete is not inside a form. the example of having validation on the md-autocomplete, and using floating label, it is used inside a form. And they are using the name of the form when using ng-messages eg ng-messages="formName.autoCompleteName.$error". I am not able to get it working with a stand alone md-autocomplete without form.

[91K00]

For me it's not working with version 1.0.1, am I the only one ?

http://codepen.io/anon/pen/obWZqP

[Wykks]

@91K00
Look at #6393

[ghost]

not working with version 1.0.6 if write required.
but with required="true" works for me according to #6393.
works with version 1.1.0-rc1.

[ghost]

It seems, the $dirty state does not work properly. Instead of focussing and unfocussing the input field, you need to type in something and remove it again. This is inconsistent compared to other input fields (and wrong as well). In addition, I have to add a seperate ng-show directive (which is different for default input fields, too).

<div ng-messages="emptyingForm.myInput.$error" ng-show="emptyingForm.myInput.$dirty">
    <div ng-message="required">Error message</div>
</div>

Hans

[ThomasBurleson]

@haenig - please do not comment on closed issues. Please open a new issue.