fix(NgModel): use string representation of the value in the ngMinlength and ngMaxlength - #7856

Fix for v1.2.x branch - #7858

I think there's something else going on. For example, if you change the model value to string, it's still not working initially. If you manipulate the model value so it's set after a short timeout, the validation works. Same when typing in the input. I think this is related to the validation being broken in some cases when the form is first compiled, see a8c7cb8

@Narretz , here is example with fixed ngMaxlength directive
http://plnkr.co/edit/MtOksjSzy5mPXpyHPiZe?p=preview

if you change the model value to string, it's still not working initially

I couldn't make that in the plunker.

Maybe there are some issues with validators, but i just fixed little bug with ngMaxlength and ngMinlength. This directives expected only strings previously, and couldn't get .length of number or object. With arrays it was tricky.

@matsko, need you here

I personally think using the viewValue as in #7968 is more consistent over the board, because some input types will not have a length property on the model.

@Narretz , I agree, using the viewValue seems the right way.

This should be fixed in master for all supported input types.